| /linux/tools/memory-model/Documentation/ |
| H A D | glossary.txt | 73 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/Documentation/devicetree/bindings/bus/ |
| H A D | xlnx,versal-net-cdx.yaml | 30 with which APU (Application Processor Unit) interacts to find out
48 phandle to the remoteproc_r5 rproc node using which APU interacts
|
| /linux/drivers/infiniband/hw/vmw_pvrdma/ |
| H A D | Kconfig | 7 RDMA adapter. It interacts with the VMXNet3 driver to provide
|
| /linux/drivers/cdx/controller/ |
| H A D | Kconfig | 16 CDX controller drives the CDX bus. It interacts with
|
| /linux/drivers/gpu/drm/i915/gt/ |
| H A D | intel_mocs.h | 23 * interacts with the contexts and the GmmLib interface.
|
| /linux/drivers/staging/greybus/Documentation/firmware/ |
| H A D | firmware-management | 49 The Firmware Management Protocol interacts with Userspace using the character
186 The Component Authentication Protocol interacts with Userspace using the
|
| /linux/drivers/phy/ti/ |
| H A D | Kconfig | 84 This driver interacts with the "OMAP Control PHY Driver" to power
|
| /linux/include/linux/ |
| H A D | mount.h | 59 * flag, consider how it interacts with shared mounts.
|
| /linux/Documentation/arch/x86/ |
| H A D | sva.rst | 157 * 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/samples/bpf/ |
| H A D | xdp_fwd_kern.c | 107 * to understand how this XDP-prog interacts with network stack. in xdp_fwd_flags()
|
| /linux/Documentation/devicetree/bindings/pinctrl/ |
| H A D | pinctrl-st.txt | 11 ST pinctrl driver controls PIO multiplexing block and also interacts with
|
| /linux/Documentation/networking/ |
| H A D | operstates.rst | 163 So basically a 802.1X supplicant interacts with the kernel like this:
|
| /linux/drivers/hwmon/ |
| H A D | nct6775-i2c.c | 8 * This driver interacts with the chip via it's "back door" i2c interface, as
|
| /linux/Documentation/driver-api/gpio/ |
| H A D | drivers-on-gpio.rst | 84 to a set of simple GPIO lines: RDY, NCE, ALE, CLE, NWP. It interacts with the
|
| /linux/scripts/lib/kdoc/ |
| H A D | kdoc_files.py | 244 Interacts over the kernel-doc results and output messages,
|
| /linux/Documentation/bpf/ |
| H A D | map_sockmap.rst | 375 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/Documentation/scsi/ |
| H A D | ufs.rst | 186 The userspace tool that interacts with the ufs-bsg endpoint and uses its
|
| /linux/kernel/ |
| H A D | kexec.c | 189 * - A generic part that interacts with the kernel and tells all of
|
| /linux/Documentation/devicetree/bindings/display/xlnx/ |
| H A D | xlnx,zynqmp-dpsub.yaml | 30 The Buffer Manager interacts with external interface such as DMA engines or
|
| /linux/Documentation/networking/device_drivers/ethernet/google/ |
| H A D | gve.rst | 37 The driver interacts with the device in the following ways:
|
| /linux/arch/parisc/include/asm/ |
| H A D | ropes.h | 20 ** Interacts with allocation granularity (ie 4 or 8 entries
|
| /linux/drivers/net/ethernet/natsemi/ |
| H A D | sonic.c | 260 * This routine interacts closely with the ISR in that it may,
265 * The ISR interacts with this routine in various ways. It may,
|
| /linux/Documentation/driver-api/pm/ |
| H A D | cpuidle.rst | 33 or platform design details in it is separate from the code that interacts with
|
| /linux/arch/x86/kvm/mmu/ |
| H A D | mmu_internal.h | 173 * KVM only interacts with sp->spt for private EPT operations. in kvm_mmu_alloc_external_spt()
|
| /linux/Documentation/dev-tools/ |
| H A D | kcov.rst | 247 interacts with some kernel interface and are usually killed when the process
|