Home
last modified time | relevance | path

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

12345678

/Linux-v5.4/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.
245 * driver that needs the interaction with graphics driver.
269 * driver that needs the interaction with graphics driver.
323 * driver that needs the interaction with graphics driver.
/Linux-v5.4/Documentation/virt/kvm/arm/
Dhyp-abi.txt3 This file documents the interaction between the Linux kernel and the
5 KVM). It doesn't cover the interaction of the kernel with the
7 hypervisor), or any hypervisor-specific interaction when the kernel is
/Linux-v5.4/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
/Linux-v5.4/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
/Linux-v5.4/Documentation/networking/
Doperstates.txt71 contains link policy. This is needed for userspace interaction
123 IF_OPER_UP if userspace interaction is disabled. Otherwise
/Linux-v5.4/drivers/staging/unisys/visorinput/
DKconfig15 and mouse interaction will not be available.
/Linux-v5.4/include/scsi/
Dscsi_transport_fc.h208 * The transport fully manages all get functions w/o driver interaction.
214 * managed by the transport w/o driver interaction.
312 * w/o driver interaction.
318 * managed by the transport w/o driver interaction.
475 * The transport fully manages all get functions w/o driver interaction.
481 * managed by the transport w/o driver interaction.
/Linux-v5.4/tools/testing/selftests/powerpc/pmu/ebb/
Dreg_access_test.c14 * kernel interaction required.
/Linux-v5.4/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.
/Linux-v5.4/drivers/ntb/test/
DKconfig26 to and from the window without additional software interaction.
/Linux-v5.4/kernel/
DKconfig.hz13 a fast response for user interaction and that may experience bus
/Linux-v5.4/Documentation/driver-api/iio/
Dintro.rst14 focused on human interaction input devices (keyboard, mouse, touchscreen).
/Linux-v5.4/fs/orangefs/
Dorangefs-dev-proto.h13 * device interaction using a common protocol
Ddowncall.h16 * Sanitized the device-client core interaction
/Linux-v5.4/tools/power/cpupower/
DREADME18 the interaction to the cpufreq core, and support for both the sysfs and proc
/Linux-v5.4/drivers/net/ethernet/dlink/
DKconfig49 Enable memory-mapped I/O for interaction with Sundance NIC registers.
/Linux-v5.4/Documentation/devicetree/bindings/soc/fsl/
Dbman-portals.txt13 interaction by software running on processor cores, accelerators and network
/Linux-v5.4/drivers/net/ethernet/sfc/
DKconfig63 driver/firmware interaction. The tracing is actually enabled by
/Linux-v5.4/arch/mips/sibyte/common/
Dcfe_console.c47 /* XXXKW think about interaction with 'console=' cmdline arg */ in cfe_console_setup()
/Linux-v5.4/drivers/gpu/drm/i915/gt/uc/
Dintel_guc_submission.h22 * GEM object is held for the entire lifetime of our interaction with
/Linux-v5.4/net/can/
DKconfig39 interaction. The BCM can be 'programmed' via the BSD socket API and
/Linux-v5.4/Documentation/x86/x86_64/
D5level-paging.rst64 One important case we need to handle here is interaction with MPX.
/Linux-v5.4/drivers/pinctrl/bcm/
DKconfig63 individually muxed to GPIO function, through interaction with the

12345678