Home
last modified time | relevance | path

Searched full:relates (Results 1 – 25 of 55) sorted by relevance

123

/Linux-v5.10/include/uapi/linux/
Diommu.h174 * relates to cache entries tagged with this PASID and matching the address
176 * - If ARCHID bit is set, @archid is populated and the invalidation relates
206 * relates to cache entries tagged with this PASID and matching the address
209 * relates to cache entries tagged with this architecture specific ID and
/Linux-v5.10/include/linux/
Dnvme-tcp.h148 * @command_id: nvme command identifier which this relates to
166 * @command_id: nvme command identifier which this relates to
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-class-bdi35 total write-back cache that relates to its current average
Dsysfs-class-uwb_rc-wusbhc23 Since this relates to security (specifically, the
/Linux-v5.10/Documentation/devicetree/bindings/iio/
Dmount-matrix.txt40 Another frame of reference is how the device with its sensor relates to the
44 becomes identical and we can focus on the data as it relates to the surrounding
/Linux-v5.10/Documentation/devicetree/bindings/media/xilinx/
Dvideo.txt22 Video IP and System Design Guide" [UG934]. How the format relates to the IP
/Linux-v5.10/Documentation/driver-api/media/
Dv4l2-intro.rst53 This is a rough schematic of how it all relates:
/Linux-v5.10/Documentation/devicetree/bindings/clock/
Dnvidia,tegra124-car.txt37 relates.
/Linux-v5.10/arch/alpha/kernel/
Dsys_eb64p.c167 * above for PCI interrupts. The IRQ relates to which bit the interrupt
Dsys_mikasa.c144 * above for PCI interrupts. The IRQ relates to which bit the interrupt
Dsys_alcor.c181 * above for PCI interrupts. The IRQ relates to which bit the interrupt
Dsys_miata.c150 * above for PCI interrupts. The IRQ relates to which bit the interrupt
Dsys_noritake.c192 * above for PCI interrupts. The IRQ relates to which bit the interrupt
/Linux-v5.10/Documentation/driver-api/80211/
Dmac80211-advanced.rst164 how it relates to mac80211 and drivers.
/Linux-v5.10/Documentation/devicetree/bindings/regulator/
Dregulator.yaml137 in microvolts, each value in the array relates to the corresponding
/Linux-v5.10/Documentation/admin-guide/
Dkernel-parameters.rst178 BUGS= Relates to possible processor bugs on the said processor.
/Linux-v5.10/drivers/net/ethernet/freescale/fman/
Dfman_mac.h198 * and phy or backplane; Note: 1000BaseX auto-negotiation relates only
/Linux-v5.10/Documentation/vm/
Dmemory-model.rst185 address ranges. The "device" aspect of `ZONE_DEVICE` relates to the fact
/Linux-v5.10/drivers/watchdog/
Dimgpdc_wdt.c25 * The following table shows how the user-configured timeout relates
/Linux-v5.10/drivers/cpufreq/
Dcpufreq-nforce2.c245 * @relation: how that frequency relates to achieved frequency
/Linux-v5.10/drivers/hv/
Dhv_balloon.c1008 * and size requirements of Linux as it relates to hot-add. in hot_add_req()
1117 * Post our status as it relates memory pressure to the
1636 * Specify our alignment requirements as it relates in balloon_connect_vsp()
/Linux-v5.10/drivers/net/wireless/intel/iwlwifi/fw/api/
Dtx.h500 * This status relates to reasons the tx might have been blocked or aborted
657 * @scd_flow: the tx queue this BA relates to
/Linux-v5.10/drivers/net/wireless/intel/iwlwifi/fw/
Dfile.h739 * @stop_conf_ids: bitmap of configurations this trigger relates to.
888 * trigger each time a time event notification that relates to time event
/Linux-v5.10/arch/alpha/include/asm/
Dcore_mcpcia.h225 * which gives 1Gbyte of accessible space which relates exactly
/Linux-v5.10/drivers/thunderbolt/
Ddma_port.c492 /* Check if the status relates to flash update auth */ in dma_port_flash_update_auth_status()

123