Searched refs:behind (Results 1 – 25 of 100) sorted by relevance
1234
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-ata | 21 connected, the number of links behind it.
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
120 "none" if no device was found behind the link.
|
| /Linux-v4.19/drivers/md/ |
| D | md-bitmap.h | 255 unsigned long sectors, int behind);
257 unsigned long sectors, int success, int behind);
|
| /Linux-v4.19/Documentation/devicetree/bindings/usb/ |
| D | ulpi.txt | 4 Phys that are behind a ULPI connection can be described with the following
|
| /Linux-v4.19/drivers/clk/versatile/ |
| D | Kconfig | 31 Express platforms hidden behind its configuration infrastructure,
|
| /Linux-v4.19/Documentation/devicetree/bindings/i2c/ |
| D | i2c-gate.txt | 23 Kasei ak8975 compass behind a gate.
|
| D | i2c-mux-ltc4306.txt | 19 multiplexers on the bus and the devices behind them use same I2C addresses.
|
| D | i2c-mux-pca954x.txt | 30 multiplexers on the bus and the devices behind them use same I2C addresses.
|
| D | i2c-mux-gpmux.txt | 37 However, I2C transactions to devices behind all I2C multiplexers connected
|
| /Linux-v4.19/Documentation/acpi/ |
| D | enumeration.txt | 5 devices behind serial bus controllers.
17 o Devices behind real busses where there is a connector resource
25 The ACPI implementation enumerates devices behind busses (platform, SPI and
142 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
224 The slaves behind I2C bus controller only need to add the ACPI IDs like
226 any slave devices behind the controller device once the adapter is
|
| /Linux-v4.19/Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 19 may be assigned to root buses behind different host bridges. The domain
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | inotify.txt | 12 Q: What is the design decision behind not tying the watch to the open fd of
21 Q: What is the design decision behind using an-fd-per-instance as opposed to
|
| /Linux-v4.19/drivers/usb/isp1760/ |
| D | Kconfig | 11 where the chip itself is behind a PLB to simulate such
|
| /Linux-v4.19/Documentation/devicetree/bindings/crypto/ |
| D | hisilicon,hip07-sec.txt | 22 - iommus: The SEC units are behind smmu-v3 iommus.
|
| /Linux-v4.19/drivers/nfc/ |
| D | Kconfig | 25 will use an HCI NFC driver for an NFC chip connected behind an
|
| /Linux-v4.19/Documentation/i2c/ |
| D | i2c-topology | 13 from the i2c bus, at least most of the time, and sits behind a gate
92 address 0x42 behind mux-one may be interleaved with a similar
93 operation targeting device address 0x42 behind mux-two. The
106 behind the mux, when an unrelated i2c transfer is in flight during
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | at91-ariag25.dts | 81 /* TWD2+TCLK2 hidden behind ethernet, so no i2c2 */
|
| /Linux-v4.19/Documentation/devicetree/bindings/memory-controllers/ |
| D | exynos-srom.txt | 10 extra properties, describing the bus behind it, should be specified as below:
|
| /Linux-v4.19/arch/alpha/lib/ |
| D | ev67-strrchr.S | 101 nop # E : hide the cmov latency (2) behind ctlz latency
|
| /Linux-v4.19/Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 12 calls, automatically behind the scenes.
|
| D | fallback-mechanisms.rst | 168 kobject uevents be issued to userspace. The original logic behind this
195 The logic behind using MAX_JIFFY_OFFSET for non-uevents is that a custom
|
| /Linux-v4.19/Documentation/networking/ |
| D | spider_net.txt | 45 flowing RX traffic, every descr behind it should be marked "full",
55 all of those behind it should be "not-in-use". When RX traffic is not
67 be "not-in-use", and everything behind it should be "empty". If no
|
| /Linux-v4.19/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 44 arrived in memory (this becomes more likely with devices behind PCI-PCI
205 2. on all devices behind a specific bridge
225 In this case, MSIs must be disabled on all devices behind the bridge.
|
| /Linux-v4.19/drivers/pci/ |
| D | Kconfig | 118 behind an IOMMU to recover from page faults.
|
| /Linux-v4.19/Documentation/RCU/ |
| D | rcu.txt | 4 The basic idea behind RCU (read-copy update) is to split destructive
|
| /Linux-v4.19/Documentation/networking/dsa/ |
| D | dsa.txt | 19 The original philosophy behind this design was to be able to use unmodified
279 non-NULL), and the switch behind it expects a tagging protocol, this network
498 out at the switch hardware for the switch to (re) learn MAC addresses behind
556 function that the driver has to call for each MAC address known to be behind
579 function that the driver has to call for each MAC address known to be behind
|
1234
