| /linux-6.14.4/Documentation/ABI/testing/ |
| D | sysfs-ata | 21 connected, the number of links behind it.
40 Behind each port, there is a ata_link. If there is a SATA PM in the topology, 15
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
67 Behind each link, up to two ata devices are created.
121 "none" if no device was found behind the link.
|
| /linux-6.14.4/drivers/md/ |
| D | raid1.h | 155 atomic_t behind_remaining; /* number of write-behind ios remaining
174 * When R1BIO_BehindIO is set, we store pages for write behind
196 /* For write-behind requests, we call bi_end_io when
197 * the last non-write-behind device completes, providing
199 * any write-behind write succeeds, otherwise we call
|
| /linux-6.14.4/tools/testing/selftests/drivers/net/mlxsw/ |
| D | tc_restrictions.sh | 215 check_fail $? "Incorrect success to add matchall rule behind a flower rule"
224 check_err $? "Failed to add flower rule behind a matchall rule"
254 # On egress, all matchall-mirror rules have to be behind the flower rules
269 check_fail $? "Incorrect success to add matchall rule behind a flower rule"
278 check_err $? "Failed to add flower rule behind a matchall rule"
|
| /linux-6.14.4/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.14.4/arch/mips/vdso/ |
| D | vgettimeofday.c | 24 * This is behind the ifdef so that we don't provide the symbol when there's no
60 * This is behind the ifdef so that we don't provide the symbol when there's no
|
| /linux-6.14.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
123 effects behind it. Thus, the order of loads and stores should not be important
|
| /linux-6.14.4/arch/sparc/kernel/ |
| D | trampoline_32.S | 50 /* Our %wim is one behind CWP */
104 /* Our %wim is one behind CWP */
163 /* Our %wim is one behind CWP */
|
| /linux-6.14.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-6.14.4/drivers/soundwire/ |
| D | debugfs.c | 153 /* Userspace changed the hardware state behind the kernel's back */ in set_command()
168 /* Userspace changed the hardware state behind the kernel's back */ in set_start_address()
187 /* Userspace changed the hardware state behind the kernel's back */ in set_num_bytes()
218 /* Userspace changed the hardware state behind the kernel's back */ in cmd_go()
|
| D | intel_ace2x_debugfs.c | 94 /* Userspace changed the hardware state behind the kernel's back */ in intel_set_m_datamode()
112 /* Userspace changed the hardware state behind the kernel's back */ in intel_set_s_datamode()
|
| /linux-6.14.4/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.14.4/drivers/firmware/efi/libstub/ |
| D | pci.c | 42 * Disregard devices living on bus 0 - these are not behind a in efi_pci_disable_bridge_busmaster()
53 * controllers that are behind a PCIe root port do not use in efi_pci_disable_bridge_busmaster()
|
| /linux-6.14.4/drivers/pci/ |
| D | irq.c | 83 * pci_swizzle_interrupt_pin - swizzle INTx for device behind bridge
87 * Perform INTx swizzling for a device behind one level of bridge. This is
89 * behind bridges on add-in cards. For devices with ARI enabled, the slot
|
| /linux-6.14.4/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.14.4/tools/perf/tests/ |
| D | maps.c | 132 /* kcore2 map hides behind bpf_prog_2 */ in test__maps__merge_in()
136 /* kcore3 map hides behind bpf_prog_3, kcore1 and adds new map */ in test__maps__merge_in()
|
| /linux-6.14.4/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
|
| /linux-6.14.4/drivers/char/agp/ |
| D | isoch.c | 61 * lying behind it...)
311 * lying behind it.
334 * (multiple AGP v3 devices are allowed behind a single bridge). in agp_3_5_enable()
382 * Take an initial pass through the devices lying behind our host in agp_3_5_enable()
|
| /linux-6.14.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
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.14.4/drivers/pci/hotplug/ |
| D | ibmphp_pci.c | 32 * If adapter is bridged, then we assign 11 to it and devices behind it.
210 …/* We need to do this in case bridge itself got configured properly, but devices behind it failed … in ibmphp_configure_card()
539 * This routine configures a PCI-2-PCI bridge and the functions behind it
583 * behind it in configure_bridge()
771 /* Now need to see how much space the devices behind the bridge needed */ in configure_bridge()
806 debug("it wants %x IO behind the bridge\n", amount_needed->io); in configure_bridge()
828 debug("it wants %x memory behind the bridge\n", amount_needed->mem); in configure_bridge()
849 debug("it wants %x pfmemory behind the bridge\n", amount_needed->pfmem); in configure_bridge()
1041 * This function adds up the amount of resources needed behind the PPB bridge
1053 int howmany = 0; /*this is to see if there are any devices behind the bridge */ in scan_behind_bridge()
[all …]
|
| /linux-6.14.4/Documentation/devicetree/bindings/usb/ |
| D | ulpi.txt | 4 Phys that are behind a ULPI connection can be described with the following
|
| /linux-6.14.4/arch/alpha/kernel/ |
| D | sys_takara.c | 168 /* These are behind the bridges. */ in takara_map_irq_srm()
182 /* Guess that we are behind a bridge. */ in takara_map_irq_srm()
238 "card-bridge behind builtin bridge yet.\n"); in takara_swizzle()
|
| /linux-6.14.4/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.14.4/drivers/clk/versatile/ |
| D | Kconfig | 29 Express platforms hidden behind its configuration infrastructure,
|
| /linux-6.14.4/drivers/gpu/drm/xe/ |
| D | xe_tile.c | 26 * a complete GPU. When multiple GPUs are placed behind a single PCI device,
43 * design (i.e., multiple GPUs behind a single PCI device); each PVC tile only
|
| /linux-6.14.4/Documentation/arch/x86/ |
| D | booting-dt.rst | 21 otherwise like interrupt routing or a list of devices behind an I2C bus.
|