/openbmc/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.
|
/openbmc/linux/tools/testing/selftests/drivers/net/bonding/ |
H A D | bond_topo_2d1c.sh | 83 # maybe called from other topologies. 105 # maybe called from other topologies.
|
/openbmc/linux/Documentation/userspace-api/media/mediactl/ |
H A D | media-controller-intro.rst | 22 approach will not scale. Device topologies are getting increasingly
|
/openbmc/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
|
/openbmc/linux/Documentation/devicetree/bindings/arm/ |
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-dummy-source.yaml | 11 specification and can be connected in various topologies to suit a particular
|
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-static-funnel.yaml | 17 specification and can be connected in various topologies to suit a particular
|
H A D | arm,coresight-dummy-sink.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-static-replicator.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-tmc.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
|
/openbmc/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.
|
/openbmc/qemu/docs/specs/ |
H A D | ppc-spapr-numa.rst | 347 * Asymmetrical topologies aren't supported. We only support NUMA topologies where 360 * 'non-transitive' topologies will be poorly translated to the guest. This is the
|
/openbmc/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
|
/openbmc/linux/Documentation/driver-api/ |
H A D | scsi.rst | 262 aproximated representation of SAS topologies in the driver model, and 263 various sysfs attributes to expose these topologies and management
|
/openbmc/linux/drivers/i2c/ |
H A D | Kconfig | 66 handle multiplexed I2C bus topologies, by presenting each
|
/openbmc/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.,
|
/openbmc/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
|
/openbmc/linux/Documentation/bpf/ |
H A D | ringbuf.rst | 63 a wide variety of topologies, from one ring buffer for each CPU (e.g., as
|
/openbmc/qemu/docs/about/ |
H A D | removed-features.rst | 197 ``-smp`` (invalid topologies) (removed in 5.2) 206 Support for invalid topologies is removed, the user must ensure 207 topologies described with -smp include all possible cpus, i.e.
|