/linux/tools/testing/selftests/net/forwarding/ ! |
H A D | README | 36 2. Ability to easily provision complex topologies. Testing bridging 49 o Tests that use anything but the most trivial topologies should include 54 multiple topologies and added to lib.sh.
|
/linux/Documentation/userspace-api/media/mediactl/ ! |
H A D | media-controller-intro.rst | 22 approach will not scale. Device topologies are getting increasingly
|
/linux/Documentation/devicetree/bindings/iio/magnetometer/ ! |
H A D | ti,tmag5273.yaml | 19 on-axis and off-axis angle measurement topologies. The angle calculation is
|
/linux/Documentation/devicetree/bindings/arm/ ! |
H A D | arm,coresight-etb10.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-tpiu.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-static-funnel.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-dummy-source.yaml | 11 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-stm.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-catu.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-dynamic-replicator.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-dynamic-funnel.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-static-replicator.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-etm.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-tmc.yaml | 17 specification and can be connected in various topologies to suit a particular
|
/linux/Documentation/i2c/ ! |
H A D | i2c-topology.rst | 2 I2C muxes and complex topologies 5 There are a couple of reasons for building more complex I2C topologies 99 It is not safe to build arbitrary topologies with two (or more) 109 but mux-locked muxes do not guarantee that in all topologies.
|
/linux/Documentation/driver-api/cxl/platform/acpi/ ! |
H A D | srat.rst | 15 supports in terms of flexible topologies.
|
/linux/Documentation/scheduler/ ! |
H A D | sched-energy.rst | 17 /!\ EAS does not support platforms with symmetric CPU topologies /!\ 19 EAS operates only on heterogeneous CPU topologies (such as Arm big.LITTLE) 330 asymmetric CPU topologies for now. This requirement is checked at run-time by
|
/linux/Documentation/driver-api/ ! |
H A D | scsi.rst | 260 approximated representation of SAS topologies in the driver model, and 261 various sysfs attributes to expose these topologies and management
|
/linux/sound/soc/intel/common/ ! |
H A D | sof-function-topology-lib.c | 123 /* Check presence of sub-topologies */ in sof_sdw_get_tplg_files()
|
/linux/drivers/i2c/ ! |
H A D | Kconfig | 58 handle multiplexed I2C bus topologies, by presenting each
|
/linux/Documentation/arch/arm/ ! |
H A D | cluster-pm-race-avoidance.rst | 515 Deep topologies: 518 support CPU topologies involving more than two levels (i.e.,
|
/linux/Documentation/networking/ ! |
H A D | phy-link-topology.rst | 28 This assumption falls apart in more complex topologies that can arise when,
|
/linux/Documentation/driver-api/cxl/ ! |
H A D | maturity-map.rst | 191 * **RCH Link Status**: RCH (Restricted CXL Host) topologies, end up
|
/linux/drivers/gpu/drm/amd/display/dc/inc/ ! |
H A D | resource.h | 336 * to recover the creation of invalid topologies. Returning false is typically 360 * to recover the creation of invalid topologies. Returning false is typically
|
/linux/drivers/ata/ ! |
H A D | libata-transport.c | 8 * an approximated representation of ATA topologies in the driver model, 9 * and various sysfs attributes to expose these topologies and management
|