Home
last modified time | relevance | path

Searched refs:behind (Results 1 – 25 of 134) sorted by relevance

123456

/Linux-v6.6/fs/ubifs/
Dmaster.c27 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-v6.6/Documentation/ABI/testing/
Dsysfs-ata21 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
121 "none" if no device was found behind the link.
/Linux-v6.6/drivers/md/
Dmd-bitmap.h256 unsigned long sectors, int behind);
258 unsigned long sectors, int success, int behind);
/Linux-v6.6/Documentation/devicetree/bindings/usb/
Dulpi.txt4 Phys that are behind a ULPI connection can be described with the following
/Linux-v6.6/Documentation/driver-api/mei/
Dnfc.rst6 Some Intel 8 and 9 Series chipsets support NFC devices connected behind
/Linux-v6.6/drivers/clk/versatile/
DKconfig29 Express platforms hidden behind its configuration infrastructure,
/Linux-v6.6/Documentation/arch/x86/
Dbooting-dt.rst21 otherwise like interrupt routing or a list of devices behind an I2C bus.
/Linux-v6.6/drivers/fsi/
DKconfig60 This option enables a FSI master that is present behind an OPB bridge
70 behind an IBM I2C Responder (I2CR) chip. The I2CR is an I2C device
/Linux-v6.6/Documentation/gpu/rfc/
Di915_gem_lmem.rst11 * Merge the uAPI bits behind special CONFIG_BROKEN(or so) flag
/Linux-v6.6/Documentation/driver-api/pci/
Dp2pdma.rst17 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-v6.6/Documentation/devicetree/bindings/i2c/
Di2c-mux-ltc4306.txt19 multiplexers on the bus and the devices behind them use same I2C addresses.
/Linux-v6.6/Documentation/devicetree/bindings/crypto/
Dhisilicon,hip07-sec.txt22 - iommus: The SEC units are behind smmu-v3 iommus.
/Linux-v6.6/Documentation/filesystems/
Dinotify.rst18 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
/Linux-v6.6/drivers/usb/isp1760/
DKconfig14 where the chip itself is behind a PLB to simulate such
/Linux-v6.6/arch/arm64/boot/dts/marvell/
Dac5-98dx25xx.dtsi208 * Dedicated section for devices behind 32bit controllers so we
211 behind-32bit-controller@7f000000 {
/Linux-v6.6/arch/arm/boot/dts/microchip/
Dat91-ariag25.dts77 /* TWD2+TCLK2 hidden behind ethernet, so no i2c2 */
/Linux-v6.6/Documentation/maintainer/
Dconfigure-git.rst41 history can find related discussions and rationale behind a certain change.
/Linux-v6.6/Documentation/firmware-guide/acpi/
Denumeration.rst9 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,
186 Slave devices behind SPI bus have SpiSerialBus resource attached to them.
261 The slaves behind I2C bus controller only need to add the ACPI IDs like
263 any slave devices behind the controller device once the adapter is
/Linux-v6.6/drivers/nfc/
DKconfig26 will use an HCI NFC driver for an NFC chip connected behind an
/Linux-v6.6/Documentation/i2c/
Di2c-topology.rst16 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
/Linux-v6.6/arch/alpha/lib/
Dev67-strrchr.S101 nop # E : hide the cmov latency (2) behind ctlz latency
/Linux-v6.6/Documentation/driver-api/firmware/
Dfirmware_cache.rst12 calls, automatically behind the scenes.
/Linux-v6.6/Documentation/networking/device_drivers/ethernet/toshiba/
Dspider_net.rst47 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
/Linux-v6.6/Documentation/PCI/
Dmsi-howto.rst49 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-v6.6/drivers/pci/
DKconfig146 behind an IOMMU to recover from page faults.
180 P2P DMA transactions must be between devices behind the same root

123456