Home
last modified time | relevance | path

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

123456

/linux/fs/ubifs/
H A 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/Documentation/ABI/testing/
H A 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/Documentation/devicetree/bindings/usb/
H A Dulpi.txt4 Phys that are behind a ULPI connection can be described with the following
/linux/drivers/fsi/
H A 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/Documentation/driver-api/mei/
H A Dnfc.rst6 Some Intel 8 and 9 Series chipsets support NFC devices connected behind
/linux/drivers/clk/versatile/
H A DKconfig29 Express platforms hidden behind its configuration infrastructure,
/linux/Documentation/arch/x86/
H A Dbooting-dt.rst21 otherwise like interrupt routing or a list of devices behind an I2C bus.
/linux/Documentation/gpu/rfc/
H A Di915_gem_lmem.rst11 * Merge the uAPI bits behind special CONFIG_BROKEN(or so) flag
/linux/Documentation/filesystems/
H A 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/Documentation/devicetree/bindings/i2c/
H A Di2c-mux-ltc4306.txt19 multiplexers on the bus and the devices behind them use same I2C addresses.
/linux/drivers/usb/isp1760/
H A DKconfig14 where the chip itself is behind a PLB to simulate such
/linux/Documentation/driver-api/cxl/linux/
H A Daccess-coordinates.rst87 For certain CXL region construction with endpoints behind CXL switches (SW) or
89 the endpoints behind a switch being more than the switch upstream link.
147 RP device. If the endpoint is behind a switch, the device pointer would be the
/linux/arch/arm64/boot/dts/marvell/
H A Dac5-98dx25xx.dtsi231 * Dedicated section for devices behind 32bit controllers so we
234 behind-32bit-controller@7f000000 {
/linux/Documentation/i2c/
H A 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/arch/arm/boot/dts/microchip/
H A Dat91-ariag25.dts77 /* TWD2+TCLK2 hidden behind ethernet, so no i2c2 */
/linux/drivers/nfc/
H A DKconfig26 will use an HCI NFC driver for an NFC chip connected behind an
/linux/Documentation/firmware-guide/acpi/
H A 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,
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
/linux/block/
H A Dbadblocks.c642 int behind) in overlap_behind() argument
646 if (bad->start < BB_OFFSET(p[behind]) && in overlap_behind()
647 (bad->start + bad->len) > BB_OFFSET(p[behind])) in overlap_behind()
/linux/Documentation/gpu/
H A Ddrm-vm-bind-async.rst121 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
/linux/arch/alpha/lib/
H A Dev67-strrchr.S101 nop # E : hide the cmov latency (2) behind ctlz latency
/linux/Documentation/driver-api/firmware/
H A Dfirmware_cache.rst12 calls, automatically behind the scenes.
/linux/Documentation/PCI/
H A 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/Documentation/networking/
H A Dnf_flowtable.rst124 netdevice behind VLAN and PPPoE netdevices. The flowtable software datapath
136 flowtable infrastructure discovers the topology behind the bridge device. This
/linux/Documentation/driver-api/
H A Dpwrseq.rst19 mitigate any potential conflicts between multiple users behind the scenes.
/linux/Documentation/driver-api/cxl/platform/
H A Dbios-and-efi.rst203 device sets (there may be multiple behind each host bridge).
207 behind the host bridge.

123456