| /linux-6.12.1/block/ |
| D | badblocks.c | 535 struct badblocks_context *bad, int behind) in can_merge_behind() argument
541 if ((s < BB_OFFSET(p[behind])) && in can_merge_behind()
542 ((s + sectors) >= BB_OFFSET(p[behind])) && in can_merge_behind()
543 ((BB_END(p[behind]) - s) <= BB_MAX_LEN) && in can_merge_behind()
544 BB_ACK(p[behind]) == bad->ack) in can_merge_behind()
555 int behind) in behind_merge()
562 WARN_ON(s >= BB_OFFSET(p[behind])); in behind_merge()
563 WARN_ON((s + sectors) < BB_OFFSET(p[behind])); in behind_merge()
565 if (s < BB_OFFSET(p[behind])) { in behind_merge()
566 merged = BB_OFFSET(p[behind]) - s; in behind_merge()
[all …]
|
| /linux-6.12.1/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-6.12.1/drivers/md/ |
| D | md-bitmap.h | 90 unsigned long sectors, bool behind);
92 unsigned long sectors, bool success, bool behind);
|
| /linux-6.12.1/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
121 "none" if no device was found behind the link.
|
| /linux-6.12.1/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
|
| /linux-6.12.1/Documentation/devicetree/bindings/usb/ |
| D | ulpi.txt | 4 Phys that are behind a ULPI connection can be described with the following
|
| /linux-6.12.1/Documentation/driver-api/mei/ |
| D | nfc.rst | 6 Some Intel 8 and 9 Series chipsets support NFC devices connected behind
|
| /linux-6.12.1/drivers/clk/versatile/ |
| D | Kconfig | 29 Express platforms hidden behind its configuration infrastructure,
|
| /linux-6.12.1/drivers/fsi/ |
| D | Kconfig | 60 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-6.12.1/Documentation/arch/x86/ |
| D | booting-dt.rst | 21 otherwise like interrupt routing or a list of devices behind an I2C bus.
|
| /linux-6.12.1/Documentation/gpu/rfc/ |
| D | i915_gem_lmem.rst | 11 * Merge the uAPI bits behind special CONFIG_BROKEN(or so) flag
|
| /linux-6.12.1/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
|
| /linux-6.12.1/Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-ltc4306.txt | 19 multiplexers on the bus and the devices behind them use same I2C addresses.
|
| /linux-6.12.1/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
|
| /linux-6.12.1/Documentation/devicetree/bindings/crypto/ |
| D | hisilicon,hip07-sec.txt | 22 - iommus: The SEC units are behind smmu-v3 iommus.
|
| /linux-6.12.1/drivers/usb/isp1760/ |
| D | Kconfig | 14 where the chip itself is behind a PLB to simulate such
|
| /linux-6.12.1/arch/arm64/boot/dts/marvell/ |
| D | ac5-98dx25xx.dtsi | 231 * Dedicated section for devices behind 32bit controllers so we
234 behind-32bit-controller@7f000000 {
|
| /linux-6.12.1/Documentation/maintainer/ |
| D | configure-git.rst | 41 history can find related discussions and rationale behind a certain change.
|
| /linux-6.12.1/arch/arm/boot/dts/microchip/ |
| D | at91-ariag25.dts | 77 /* TWD2+TCLK2 hidden behind ethernet, so no i2c2 */
|
| /linux-6.12.1/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
|
| /linux-6.12.1/drivers/nfc/ |
| D | Kconfig | 26 will use an HCI NFC driver for an NFC chip connected behind an
|
| /linux-6.12.1/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
|
| /linux-6.12.1/arch/alpha/lib/ |
| D | ev67-strrchr.S | 101 nop # E : hide the cmov latency (2) behind ctlz latency
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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
|