Searched full:behind (Results 1 – 25 of 117) sorted by relevance
12345
| /Documentation/ABI/testing/ |
| D | sysfs-ata | 21 connected, the number of links behind it.
40 Behind each port, there is a ata_link. If there is a SATA PM in the topology, 15
43 If a link is behind a port, the directory name is linkX, where X is ata_port_id
44 of the port. If a link is behind a PM, its name is linkX.Y where X is
67 Behind each link, up to two ata devices are created.
121 "none" if no device was found behind the link.
|
| /Documentation/driver-api/cxl/ |
| D | access-coordinates.rst | 10 For certain CXL region construction with endpoints behind CXL switches (SW) or
12 the endpoints behind a switch being more than the switch upstream link.
70 RP device. If the endpoint is behind a switch, the device pointer would be the
|
| /Documentation/devicetree/bindings/usb/ |
| D | ulpi.txt | 4 Phys that are behind a ULPI connection can be described with the following
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 17 only supports doing P2P when the endpoints involved are all behind the
61 memory behind it, its driver could add support as a P2P provider and
123 effects behind it. Thus, the order of loads and stores should not be important
|
| /Documentation/arch/x86/ |
| D | booting-dt.rst | 21 otherwise like interrupt routing or a list of devices behind an I2C bus.
|
| /Documentation/driver-api/mei/ |
| D | nfc.rst | 6 Some Intel 8 and 9 Series chipsets support NFC devices connected behind
|
| /Documentation/gpu/rfc/ |
| D | i915_gem_lmem.rst | 11 * Merge the uAPI bits behind special CONFIG_BROKEN(or so) flag
|
| /Documentation/filesystems/ |
| D | inotify.rst | 18 What is the design decision behind not tying the watch to the open fd of
29 What is the design decision behind using an-fd-per-instance as opposed to
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-ltc4306.txt | 19 multiplexers on the bus and the devices behind them use same I2C addresses.
|
| D | i2c-mux-pca954x.yaml | 64 the devices behind them use same I2C addresses.
|
| D | i2c-mux-gpmux.yaml | 59 However, I2C transactions to devices behind all I2C multiplexers connected
|
| /Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 47 flowing RX traffic, every descr behind it should be marked "full",
57 all of those behind it should be "not-in-use". When RX traffic is not
69 be "not-in-use", and everything behind it should be "empty". If no
|
| /Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 12 calls, automatically behind the scenes.
|
| /Documentation/maintainer/ |
| D | configure-git.rst | 41 history can find related discussions and rationale behind a certain change.
|
| /Documentation/devicetree/bindings/crypto/ |
| D | hisilicon,hip07-sec.txt | 22 - iommus: The SEC units are behind smmu-v3 iommus.
|
| /Documentation/gpu/ |
| D | drm-vm-bind-async.rst | 121 deeply pipelined behind other VM_BIND operations and workloads
123 subsequent VM_BIND operation to be queued behind the first one if
140 buffers. The workload execution can then easily be pipelined behind
|
| /Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 9 devices behind serial bus controllers.
21 - Devices behind real busses where there is a connector resource
30 The ACPI implementation enumerates devices behind busses (platform, SPI,
229 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
304 The slaves behind I2C bus controller only need to add the ACPI IDs like
306 any slave devices behind the controller device once the adapter is
|
| /Documentation/PCI/ |
| D | msi-howto.rst | 49 arrived in memory (this becomes more likely with devices behind PCI-PCI
218 2. on all devices behind a specific bridge
240 In this case, MSIs must be disabled on all devices behind the bridge.
|
| /Documentation/driver-api/ |
| D | pwrseq.rst | 19 mitigate any potential conflicts between multiple users behind the scenes.
|
| /Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 19 may be assigned to root buses behind different host bridges. The domain
|
| /Documentation/networking/ |
| D | nf_flowtable.rst | 124 netdevice behind VLAN and PPPoE netdevices. The flowtable software datapath
136 flowtable infrastructure discovers the topology behind the bridge device. This
|
| /Documentation/RCU/ |
| D | rcu.rst | 6 The basic idea behind RCU (read-copy update) is to split destructive
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | exynos-srom.yaml | 14 extra properties, describing the bus behind it, should be specified.
|
| /Documentation/process/ |
| D | 3.Early-stage.rst | 96 clear lesson: kernel code which is designed and developed behind closed
208 need to keep development plans behind closed doors.
|
| /Documentation/i2c/ |
| D | i2c-topology.rst | 16 from the I2C bus, at least most of the time, and sits behind a gate
105 address 0x42 behind mux-one may be interleaved with a similar
106 operation targeting device address 0x42 behind mux-two. The
121 behind the mux, when an unrelated I2C transfer is in flight during
|
12345