Home
last modified time | relevance | path

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

12345678910

/Linux-v6.1/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.
/Linux-v6.1/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
/Linux-v6.1/Documentation/dev-tools/kunit/
Dfaq.rst54 - An integration test tests the interaction between a minimal set of components,
56 test to test the interaction between a driver and a piece of hardware, or to
57 test the interaction between the userspace libraries the kernel provides and
/Linux-v6.1/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-v6.1/drivers/net/dsa/hirschmann/
Dhellcreek_hwtstamp.c50 /* Interaction with the timestamp hardware is prevented here. It is in hellcreek_set_hwtstamp_config()
105 * enable the interaction with the HW timestamping in hellcreek_set_hwtstamp_config()
388 * and the interaction with the HW timestamping is enabled. If not, stop in hellcreek_port_txtstamp()
431 * and the interaction with the HW timestamping is enabled. If not, stop in hellcreek_port_rxtstamp()
/Linux-v6.1/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-v6.1/drivers/misc/uacce/
DKconfig6 without interaction with the kernel space in data path.
/Linux-v6.1/tools/testing/selftests/powerpc/pmu/ebb/
Dreg_access_test.c14 * kernel interaction required.
/Linux-v6.1/include/scsi/
Dscsi_transport_fc.h210 * The transport fully manages all get functions w/o driver interaction.
216 * managed by the transport w/o driver interaction.
344 * w/o driver interaction.
350 * managed by the transport w/o driver interaction.
511 * The transport fully manages all get functions w/o driver interaction.
517 * managed by the transport w/o driver interaction.
/Linux-v6.1/Documentation/networking/
Doperstates.rst92 contains link policy. This is needed for userspace interaction
145 IF_OPER_UP if userspace interaction is disabled. Otherwise
/Linux-v6.1/Documentation/scheduler/
Dschedutil.rst152 interaction should be 'fast' and non-blocking. Schedutil supports
153 rate-limiting DVFS requests for when hardware interaction is slow and
/Linux-v6.1/drivers/ntb/test/
DKconfig26 to and from the window without additional software interaction.
/Linux-v6.1/arch/arm/mach-at91/
Dsam_secure.c42 * OP-TEE kernel driver is not needed for the type of interaction made in sam_secure_init()
/Linux-v6.1/kernel/
DKconfig.hz13 a fast response for user interaction and that may experience bus
/Linux-v6.1/drivers/net/ethernet/sfc/siena/
DKconfig44 driver/firmware interaction. The tracing is actually enabled by
/Linux-v6.1/fs/orangefs/
Dorangefs-dev-proto.h13 * device interaction using a common protocol
/Linux-v6.1/Documentation/driver-api/iio/
Dintro.rst14 focused on human interaction input devices (keyboard, mouse, touchscreen).
/Linux-v6.1/drivers/net/ethernet/dlink/
DKconfig49 Enable memory-mapped I/O for interaction with Sundance NIC registers.
/Linux-v6.1/tools/power/cpupower/
DREADME18 the interaction to the cpufreq core, and support for both the sysfs and proc
/Linux-v6.1/Documentation/devicetree/bindings/soc/fsl/
Dbman-portals.txt13 interaction by software running on processor cores, accelerators and network
/Linux-v6.1/Documentation/devicetree/bindings/gpio/
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-v6.1/Documentation/devicetree/bindings/pinctrl/
Dpinctrl.yaml24 whether there is any interaction between the child and intermediate parent
/Linux-v6.1/Documentation/ABI/testing/
Drtc-cdev41 need user interaction when the backup power provider is
/Linux-v6.1/drivers/net/ethernet/sfc/
DKconfig64 driver/firmware interaction. The tracing is actually enabled by

12345678910