Home
last modified time | relevance | path

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

123

/Linux-v6.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-v6.1/drivers/infiniband/hw/vmw_pvrdma/
DKconfig7 RDMA adapter. It interacts with the VMXNet3 driver to provide
/Linux-v6.1/drivers/gpu/drm/i915/gt/
Dintel_mocs.h23 * interacts with the contexts and the GmmLib interface.
/Linux-v6.1/arch/um/kernel/skas/
Dsyscall.c25 * went to sleep, even if said userspace interacts with the kernel in in handle_syscall()
/Linux-v6.1/drivers/phy/ti/
DKconfig84 This driver interacts with the "OMAP Control PHY Driver" to power
/Linux-v6.1/Documentation/admin-guide/media/
Ddavinci-vpbe.rst58 features. The VPBE module interacts with the OSD for enabling and
/Linux-v6.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-v6.1/include/linux/
Dmount.h43 * flag, consider how it interacts with shared mounts.
/Linux-v6.1/Documentation/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-v6.1/Documentation/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-v6.1/samples/bpf/
Dxdp_fwd_kern.c107 * to understand how this XDP-prog interacts with network stack. in xdp_fwd_flags()
/Linux-v6.1/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-st.txt11 ST pinctrl driver controls PIO multiplexing block and also interacts with
/Linux-v6.1/Documentation/devicetree/bindings/display/xlnx/
Dxlnx,zynqmp-dpsub.yaml30 The Buffer Manager interacts with external interface such as DMA engines or
/Linux-v6.1/Documentation/driver-api/gpio/
Ddrivers-on-gpio.rst79 to a set of simple GPIO lines: RDY, NCE, ALE, CLE, NWP. It interacts with the
/Linux-v6.1/Documentation/networking/
Doperstates.rst163 So basically a 802.1X supplicant interacts with the kernel like this:
/Linux-v6.1/Documentation/process/
Dcode-of-conduct-interpretation.rst89 The Linux kernel community primarily interacts on a set of public email
/Linux-v6.1/drivers/hwmon/
Dnct6775-i2c.c8 * This driver interacts with the chip via it's "back door" i2c interface, as
/Linux-v6.1/kernel/
Dkexec.c177 * - A generic part that interacts with the kernel and tells all of
/Linux-v6.1/Documentation/scsi/
Dufs.rst186 The userspace tool that interacts with the ufs-bsg endpoint and uses its
/Linux-v6.1/Documentation/admin-guide/mm/
Dzswap.rst18 Zswap is a new feature as of v3.11 and interacts heavily with memory
/Linux-v6.1/Documentation/networking/device_drivers/ethernet/google/
Dgve.rst37 The driver interacts with the device in the following ways:
/Linux-v6.1/Documentation/gpu/amdgpu/
Ddriver-core.rst53 SoC. The driver interacts with it to control power management
/Linux-v6.1/drivers/gpu/drm/msm/
Dmsm_gpu_devfreq.c101 /* simple_ondemand governor interacts poorly with gpu->clamp_to_idle. in update_average_dev_status()
/Linux-v6.1/arch/parisc/include/asm/
Dropes.h20 ** Interacts with allocation granularity (ie 4 or 8 entries
/Linux-v6.1/Documentation/networking/device_drivers/ethernet/marvell/
Docteontx2.rst76 AF driver also interacts with underlying firmware to

123