Home
last modified time | relevance | path

Searched full:interaction (Results 1 – 25 of 170) sorted by relevance

1234567

/linux/Documentation/virt/kvm/arm/
H A Dhyp-abi.rst7 This file documents the interaction between the Linux kernel and the
9 KVM). It doesn't cover the interaction of the kernel with the
11 hypervisor), or any hypervisor-specific interaction when the kernel is
/linux/tools/testing/selftests/livepatch/
H A Dtest-kprobe.sh19 start_test "livepatch interaction with kprobed function with post_handler"
40 start_test "livepatch interaction with kprobed function without post_handler"
H A Dtest-ftrace.sh17 start_test "livepatch interaction with ftrace_enabled sysctl"
/linux/Documentation/sound/designs/
H A Dtracepoints.rst34 interaction between applications and ALSA PCM core. Once decided, runtime of
123 Each driver can join in the interaction as long as it prepared for two stuffs
133 The driver can refers to result of the interaction in a callback of
/linux/Documentation/driver-api/
H A Ds390-drivers.rst12 for interaction with the hardware and interfaces for interacting with
74 Interaction with the driver core is done via the common I/O layer, which
/linux/drivers/misc/uacce/
H A DKconfig6 without interaction with the kernel space in data path.
/linux/tools/testing/selftests/powerpc/pmu/ebb/
H A Dreg_access_test.c14 * kernel interaction required.
/linux/Documentation/scheduler/
H A Dschedutil.rst151 interaction should be 'fast' and non-blocking. Schedutil supports
152 rate-limiting DVFS requests for when hardware interaction is slow and
/linux/Documentation/networking/
H A Doperstates.rst92 contains link policy. This is needed for userspace interaction
145 IF_OPER_UP if userspace interaction is disabled. Otherwise
/linux/drivers/ntb/test/
H A DKconfig26 to and from the window without additional software interaction.
/linux/arch/arm/mach-at91/
H A Dsam_secure.c42 * OP-TEE kernel driver is not needed for the type of interaction made in sam_secure_init()
/linux/drivers/net/ethernet/sfc/siena/
H A DKconfig44 driver/firmware interaction. The tracing is actually enabled by
/linux/Documentation/driver-api/iio/
H A Dintro.rst14 focused on human interaction input devices (keyboard, mouse, touchscreen).
/linux/fs/orangefs/
H A Dorangefs-dev-proto.h13 * device interaction using a common protocol
H A Ddowncall.h16 * Sanitized the device-client core interaction
/linux/Documentation/devicetree/bindings/soc/fsl/
H A Dfsl,bman-portal.yaml16 interaction by software running on processor cores, accelerators and network
/linux/tools/testing/selftests/arm64/gcs/
H A DMakefile4 # In order to avoid interaction with the toolchain and dynamic linker the
/linux/drivers/net/ethernet/dlink/
H A DKconfig49 Enable memory-mapped I/O for interaction with Sundance NIC registers.
/linux/security/landlock/errata/
H A Dabi-6.h15 * interaction between threads of the same process should always be allowed.
/linux/Documentation/ABI/testing/
H A Drtc-cdev41 need user interaction when the backup power provider is
/linux/arch/mips/sibyte/common/
H A Dcfe_console.c47 /* XXXKW think about interaction with 'console=' cmdline arg */ in cfe_console_setup()
/linux/Documentation/mhi/
H A Dtopology.rst13 MHI controller driver manages the interaction with the MHI client devices
/linux/drivers/net/ethernet/sfc/
H A DKconfig67 driver/firmware interaction. The tracing is actually enabled by
/linux/sound/hda/common/
H A DKconfig29 If you need the traditional sysfs entries for the manual interaction,
/linux/net/can/
H A DKconfig40 interaction. The BCM can be 'programmed' via the BSD socket API and

1234567