Home
last modified time | relevance | path

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

123

/Linux-v5.10/drivers/infiniband/hw/vmw_pvrdma/
DKconfig7 RDMA adapter. It interacts with the VMXNet3 driver to provide
/Linux-v5.10/arch/um/kernel/skas/
Dsyscall.c25 * went to sleep, even if said userspace interacts with the kernel in in handle_syscall()
/Linux-v5.10/drivers/gpu/drm/i915/gt/
Dintel_mocs.h41 * interacts with the contexts and the GmmLib interface.
/Linux-v5.10/Documentation/admin-guide/media/
Ddavinci-vpbe.rst58 features. The VPBE module interacts with the OSD for enabling and
/Linux-v5.10/drivers/phy/ti/
DKconfig84 This driver interacts with the "OMAP Control PHY Driver" to power
/Linux-v5.10/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-v5.10/Documentation/x86/
Dsva.rst128 * For each device with which a process interacts, there must be
240 device. When removing pages, it interacts with the device to remove any
/Linux-v5.10/include/linux/
Dmount.h45 * flag, consider how it interacts with shared mounts.
/Linux-v5.10/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-v5.10/samples/bpf/
Dxdp_fwd_kern.c107 * to understand how this XDP-prog interacts with network stack. in xdp_fwd_flags()
/Linux-v5.10/Documentation/devicetree/bindings/display/xlnx/
Dxlnx,zynqmp-dpsub.yaml30 The Buffer Manager interacts with external interface such as DMA engines or
/Linux-v5.10/Documentation/devicetree/bindings/pinctrl/
Dpinctrl-st.txt11 ST pinctrl driver controls PIO multiplexing block and also interacts with
/Linux-v5.10/Documentation/networking/device_drivers/ethernet/google/
Dgve.rst37 The driver interacts with the device in the following ways:
/Linux-v5.10/Documentation/networking/
Doperstates.rst161 So basically a 802.1X supplicant interacts with the kernel like this:
/Linux-v5.10/Documentation/process/
Dcode-of-conduct-interpretation.rst89 The Linux kernel community primarily interacts on a set of public email
/Linux-v5.10/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-v5.10/Documentation/scsi/
Dufs.rst184 The userspace tool that interacts with the ufs-bsg endpoint and uses its
/Linux-v5.10/Documentation/vm/
Dzswap.rst18 Zswap is a new feature as of v3.11 and interacts heavily with memory
/Linux-v5.10/Documentation/networking/device_drivers/ethernet/marvell/
Docteontx2.rst75 AF driver also interacts with underlying firmware to
/Linux-v5.10/kernel/
Dkexec.c185 * - A generic part that interacts with the kernel and tells all of
/Linux-v5.10/arch/parisc/include/asm/
Dropes.h20 ** Interacts with allocation granularity (ie 4 or 8 entries
/Linux-v5.10/drivers/dma-buf/
Ddma-fence.c185 * differences. &dma_fence interacts with almost all of the core memory
187 * dma_resv_unlock(). On the other side it also interacts through all
/Linux-v5.10/drivers/net/ethernet/natsemi/
Dsonic.c260 * This routine interacts closely with the ISR in that it may,
265 * The ISR interacts with this routine in various ways. It may,
/Linux-v5.10/Documentation/dev-tools/
Dkcov.rst219 USB HCD); and the local ones, that are spawned when a user interacts with
/Linux-v5.10/Documentation/driver-api/pm/
Dcpuidle.rst33 or platform design details in it is separate from the code that interacts with

123