/linux/Documentation/virt/kvm/arm/ |
H A D | hyp-abi.rst | 7 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 D | test-kprobe.sh | 19 start_test "livepatch interaction with kprobed function with post_handler" 40 start_test "livepatch interaction with kprobed function without post_handler"
|
/linux/Documentation/dev-tools/kunit/ |
H A D | faq.rst | 54 - 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/Documentation/sound/designs/ |
H A D | tracepoints.rst | 34 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/include/scsi/ |
H A D | scsi_transport_fc.h | 210 * 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. 512 * The transport fully manages all get functions w/o driver interaction. 518 * managed by the transport w/o driver interaction.
|
/linux/Documentation/driver-api/ |
H A D | s390-drivers.rst | 12 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/virt/coco/pkvm-guest/ |
H A D | Kconfig | 7 interaction with virtual devices. This driver implements
|
/linux/drivers/misc/uacce/ |
H A D | Kconfig | 6 without interaction with the kernel space in data path.
|
/linux/Documentation/scheduler/ |
H A D | schedutil.rst | 151 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 D | operstates.rst | 92 contains link policy. This is needed for userspace interaction 145 IF_OPER_UP if userspace interaction is disabled. Otherwise
|
/linux/tools/testing/selftests/powerpc/pmu/ebb/ |
H A D | reg_access_test.c | 14 * kernel interaction required.
|
/linux/drivers/ntb/test/ |
H A D | Kconfig | 26 to and from the window without additional software interaction.
|
/linux/arch/arm/mach-at91/ |
H A D | sam_secure.c | 42 * 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 D | Kconfig | 44 driver/firmware interaction. The tracing is actually enabled by
|
/linux/Documentation/driver-api/iio/ |
H A D | intro.rst | 14 focused on human interaction input devices (keyboard, mouse, touchscreen).
|
/linux/fs/orangefs/ |
H A D | orangefs-dev-proto.h | 13 * device interaction using a common protocol
|
H A D | downcall.h | 16 * Sanitized the device-client core interaction
|
/linux/Documentation/devicetree/bindings/soc/fsl/ |
H A D | fsl,bman-portal.yaml | 16 interaction by software running on processor cores, accelerators and network
|
/linux/Documentation/devicetree/bindings/pinctrl/ |
H A D | pinctrl.yaml | 24 whether there is any interaction between the child and intermediate parent
|
/linux/Documentation/devicetree/bindings/gpio/ |
H A D | microchip,pic32-gpio.txt | 23 - gpio-ranges: Interaction with the PINCTRL subsystem.
|
/linux/Documentation/ABI/testing/ |
H A D | rtc-cdev | 41 need user interaction when the backup power provider is
|
/linux/drivers/net/ethernet/sfc/ |
H A D | Kconfig | 67 driver/firmware interaction. The tracing is actually enabled by
|
/linux/arch/mips/sibyte/common/ |
H A D | cfe_console.c | 47 /* XXXKW think about interaction with 'console=' cmdline arg */ in cfe_console_setup()
|
/linux/Documentation/mhi/ |
H A D | topology.rst | 13 MHI controller driver manages the interaction with the MHI client devices
|
/linux/net/can/ |
H A D | Kconfig | 39 interaction. The BCM can be 'programmed' via the BSD socket API and
|