Home
last modified time | relevance | path

Searched full:interacts (Results 1 – 25 of 65) sorted by relevance

123

/linux-6.12.1/tools/memory-model/Documentation/
Dglossary.txt73 In a cycle, each CPU's ordering interacts with that of the next:
80 CPU 0's smp_mb() interacts with that of CPU 1, which interacts
81 with that of CPU 2, which in turn interacts with that of CPU 0
/linux-6.12.1/Documentation/devicetree/bindings/bus/
Dxlnx,versal-net-cdx.yaml30 with which APU (Application Processor Unit) interacts to find out
48 phandle to the remoteproc_r5 rproc node using which APU interacts
/linux-6.12.1/drivers/infiniband/hw/vmw_pvrdma/
DKconfig7 RDMA adapter. It interacts with the VMXNet3 driver to provide
/linux-6.12.1/drivers/cdx/controller/
DKconfig16 CDX controller drives the CDX bus. It interacts with
/linux-6.12.1/tools/perf/tests/workloads/
Ddatasym.c30 * longer a continuous repeating pattern that interacts in datasym()
/linux-6.12.1/drivers/gpu/drm/i915/gt/
Dintel_mocs.h23 * interacts with the contexts and the GmmLib interface.
/linux-6.12.1/Documentation/networking/device_drivers/ethernet/meta/
Dfbnic.rst15 This is the firmware which fbnic_fw.c interacts with.
/linux-6.12.1/drivers/phy/ti/
DKconfig84 This driver interacts with the "OMAP Control PHY Driver" to power
/linux-6.12.1/drivers/staging/greybus/Documentation/firmware/
Dfirmware-management49 The Firmware Management Protocol interacts with Userspace using the character
186 The Component Authentication Protocol interacts with Userspace using the
/linux-6.12.1/include/linux/
Dmount.h44 * flag, consider how it interacts with shared mounts.
/linux-6.12.1/Documentation/arch/x86/
Dsva.rst157 * For each device with which a process interacts, there must be
269 device. When removing pages, it interacts with the device to remove any
/linux-6.12.1/Documentation/arch/powerpc/
Dcxl.rst54 of the AFU. Only userspace interacts directly with the AFU.
57 AFU needs. This is what the kernel interacts with. For example, if
/linux-6.12.1/samples/bpf/
Dxdp_fwd_kern.c107 * to understand how this XDP-prog interacts with network stack. in xdp_fwd_flags()
/linux-6.12.1/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-st.txt11 ST pinctrl driver controls PIO multiplexing block and also interacts with
/linux-6.12.1/Documentation/process/
Dcode-of-conduct-interpretation.rst89 The Linux kernel community primarily interacts on a set of public email
/linux-6.12.1/Documentation/networking/
Doperstates.rst163 So basically a 802.1X supplicant interacts with the kernel like this:
/linux-6.12.1/drivers/hwmon/
Dnct6775-i2c.c8 * This driver interacts with the chip via it's "back door" i2c interface, as
/linux-6.12.1/Documentation/driver-api/gpio/
Ddrivers-on-gpio.rst84 to a set of simple GPIO lines: RDY, NCE, ALE, CLE, NWP. It interacts with the
/linux-6.12.1/Documentation/devicetree/bindings/display/xlnx/
Dxlnx,zynqmp-dpsub.yaml30 The Buffer Manager interacts with external interface such as DMA engines or
/linux-6.12.1/Documentation/scsi/
Dufs.rst186 The userspace tool that interacts with the ufs-bsg endpoint and uses its
/linux-6.12.1/Documentation/gpu/amdgpu/
Ddriver-core.rst53 SoC. The driver interacts with it to control power management
/linux-6.12.1/kernel/
Dkexec.c189 * - A generic part that interacts with the kernel and tells all of
/linux-6.12.1/Documentation/bpf/
Dmap_sockmap.rst375 The following code snippet shows a simple verdict program that interacts with a
410 The following code snippet shows a simple verdict program that interacts with a
/linux-6.12.1/Documentation/networking/device_drivers/ethernet/google/
Dgve.rst37 The driver interacts with the device in the following ways:
/linux-6.12.1/arch/parisc/include/asm/
Dropes.h20 ** Interacts with allocation granularity (ie 4 or 8 entries

123