Searched refs:behind (Results 1 – 25 of 103) sorted by relevance
12345
| /Linux-v5.4/fs/ubifs/ |
| D | master.c | 27 int behind; in ubifs_compare_master_node() local
43 behind = hmac_offs + UBIFS_MAX_HMAC_LEN; in ubifs_compare_master_node()
45 if (UBIFS_MST_NODE_SZ > behind) in ubifs_compare_master_node()
46 return memcmp(m1 + behind, m2 + behind, UBIFS_MST_NODE_SZ - behind); in ubifs_compare_master_node()
|
| /Linux-v5.4/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-v5.4/drivers/md/ |
| D | md-bitmap.h | 255 unsigned long sectors, int behind);
257 unsigned long sectors, int success, int behind);
|
| /Linux-v5.4/Documentation/devicetree/bindings/usb/ |
| D | ulpi.txt | 4 Phys that are behind a ULPI connection can be described with the following
|
| /Linux-v5.4/Documentation/driver-api/mei/ |
| D | nfc.rst | 6 Some Intel 8 and 9 Serieses chipsets supports NFC devices connected behind
|
| /Linux-v5.4/drivers/clk/versatile/ |
| D | Kconfig | 32 Express platforms hidden behind its configuration infrastructure,
|
| /Linux-v5.4/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-v5.4/Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 9 devices behind serial bus controllers.
21 - Devices behind real busses where there is a connector resource
29 The ACPI implementation enumerates devices behind busses (platform, SPI and
149 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
232 The slaves behind I2C bus controller only need to add the ACPI IDs like
234 any slave devices behind the controller device once the adapter is
|
| /Linux-v5.4/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
133 effects behind it. Thus, the order of loads and stores should not be important
|
| /Linux-v5.4/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-v5.4/Documentation/devicetree/bindings/crypto/ |
| D | hisilicon,hip07-sec.txt | 22 - iommus: The SEC units are behind smmu-v3 iommus.
|
| /Linux-v5.4/drivers/usb/isp1760/ |
| D | Kconfig | 13 where the chip itself is behind a PLB to simulate such
|
| /Linux-v5.4/drivers/nfc/ |
| D | Kconfig | 26 will use an HCI NFC driver for an NFC chip connected behind an
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | at91-ariag25.dts | 77 /* TWD2+TCLK2 hidden behind ethernet, so no i2c2 */
|
| /Linux-v5.4/drivers/pci/ |
| D | Kconfig | 145 behind an IOMMU to recover from page faults.
173 P2P DMA transactions must be between devices behind the same root
|
| /Linux-v5.4/Documentation/i2c/ |
| D | i2c-topology.rst | 14 from the i2c bus, at least most of the time, and sits behind a gate
104 address 0x42 behind mux-one may be interleaved with a similar
105 operation targeting device address 0x42 behind mux-two. The
118 behind the mux, when an unrelated i2c transfer is in flight during
|
| /Linux-v5.4/Documentation/devicetree/bindings/memory-controllers/ |
| D | exynos-srom.txt | 10 extra properties, describing the bus behind it, should be specified as below:
|
| /Linux-v5.4/arch/alpha/lib/ |
| D | ev67-strrchr.S | 101 nop # E : hide the cmov latency (2) behind ctlz latency
|
| /Linux-v5.4/Documentation/driver-api/firmware/ |
| D | firmware_cache.rst | 12 calls, automatically behind the scenes.
|
| /Linux-v5.4/Documentation/networking/device_drivers/toshiba/ |
| 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-v5.4/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.
|
| /Linux-v5.4/Documentation/devicetree/bindings/pci/ |
| D | pci.txt | 19 may be assigned to root buses behind different host bridges. The domain
|
12345
