Home
last modified time | relevance | path

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

123456789

/kernel/linux/linux-5.10/sound/hda/
Dhdac_component.c28 * driver that needs the interaction with graphics driver.
61 * needs the interaction with graphics driver.
116 * driver that needs the interaction with graphics driver.
151 * driver that needs the interaction with graphics driver.
247 * driver that needs the interaction with graphics driver.
272 * driver that needs the interaction with graphics driver.
327 * driver that needs the interaction with graphics driver.
/kernel/linux/linux-5.10/Documentation/virt/kvm/arm/
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
/kernel/linux/linux-5.10/Documentation/dev-tools/kunit/
Dfaq.rst52 - An integration test tests the interaction between a minimal set of components,
54 test to test the interaction between a driver and a piece of hardware, or to
55 test the interaction between the userspace libraries the kernel provides and
/kernel/linux/linux-5.10/Documentation/sound/designs/
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
/kernel/linux/linux-5.10/drivers/misc/uacce/
DKconfig6 without interaction with the kernel space in data path.
/kernel/linux/linux-5.10/Documentation/driver-api/
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
/kernel/linux/linux-5.10/drivers/staging/unisys/visorinput/
DKconfig15 and mouse interaction will not be available.
/kernel/linux/linux-5.10/include/scsi/
Dscsi_transport_fc.h209 * The transport fully manages all get functions w/o driver interaction.
215 * managed by the transport w/o driver interaction.
313 * w/o driver interaction.
319 * managed by the transport w/o driver interaction.
476 * The transport fully manages all get functions w/o driver interaction.
482 * managed by the transport w/o driver interaction.
/kernel/linux/linux-5.10/tools/testing/selftests/powerpc/pmu/ebb/
Dreg_access_test.c14 * kernel interaction required.
/kernel/linux/linux-5.10/include/linux/soundwire/
Dsdw_intel.h12 * the @params_stream callback, e.g. for interaction with DSP
25 * the @free_stream callback, e.g. for interaction with DSP
/kernel/linux/linux-5.10/Documentation/networking/
Doperstates.rst90 contains link policy. This is needed for userspace interaction
143 IF_OPER_UP if userspace interaction is disabled. Otherwise
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/
Dzx296702-gpio.txt10 - gpio-ranges : Interaction with the PINCTRL subsystem.
Dgpio_oxnas.txt22 - gpio-ranges: Interaction with the PINCTRL subsystem, it also specifies the
Dmicrochip,pic32-gpio.txt23 - gpio-ranges: Interaction with the PINCTRL subsystem.
/kernel/linux/linux-5.10/drivers/ntb/test/
DKconfig26 to and from the window without additional software interaction.
/kernel/linux/linux-5.10/kernel/
DKconfig.hz13 a fast response for user interaction and that may experience bus
/kernel/linux/linux-5.10/drivers/net/ethernet/dlink/
DKconfig49 Enable memory-mapped I/O for interaction with Sundance NIC registers.
/kernel/linux/linux-5.10/Documentation/driver-api/iio/
Dintro.rst14 focused on human interaction input devices (keyboard, mouse, touchscreen).
/kernel/linux/linux-5.10/fs/orangefs/
Dorangefs-dev-proto.h13 * device interaction using a common protocol
/kernel/linux/linux-5.10/tools/power/cpupower/
DREADME18 the interaction to the cpufreq core, and support for both the sysfs and proc
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/fsl/
Dbman-portals.txt13 interaction by software running on processor cores, accelerators and network
/kernel/linux/linux-5.10/tools/testing/selftests/livepatch/
Dtest-ftrace.sh16 start_test "livepatch interaction with ftrace_enabled sysctl"
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Drtc-cdev41 need user interaction when the backup power provider is
/kernel/linux/linux-5.10/drivers/net/ethernet/sfc/
DKconfig64 driver/firmware interaction. The tracing is actually enabled by
/kernel/linux/linux-5.10/arch/mips/sibyte/common/
Dcfe_console.c47 /* XXXKW think about interaction with 'console=' cmdline arg */ in cfe_console_setup()

123456789