Home
last modified time | relevance | path

Searched full:implementing (Results 1 – 25 of 508) sorted by relevance

12345678910>>...21

/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-class-regulator257 implementing suspend voltage configuration constraints.
268 implementing suspend voltage configuration constraints.
279 implementing suspend voltage configuration constraints.
289 memory, for regulators implementing suspend mode
300 for regulators implementing suspend mode configuration
311 standby, for regulators implementing suspend mode
321 when suspended to memory, for regulators implementing suspend
334 when suspended to disk, for regulators implementing
347 state when suspended to standby, for regulators implementing
Dsysfs-block-device72 (HBA) implementing support for the SATA NCQ priority feature.
94 (HBA) implementing support for the SATA NCQ priority feature.
/linux-6.14.4/Documentation/networking/device_drivers/wwan/
Dt7xx.rst103 The driver exposes an MBIM interface to the MBIM function by implementing
147 The driver exposes an AT port by implementing AT WWAN Port.
156 The driver exposes a fastboot protocol interface by implementing
170 The driver exposes a ADB protocol interface by implementing ADB WWAN Port.
179 The driver exposes a diagnostic interface by implementing MIPC (Modem
/linux-6.14.4/net/hsr/
DKconfig13 DANH ("Doubly attached node implementing HSR") or DANP ("Doubly
14 attached node implementing PRP"). For this to work, your Linux box
/linux-6.14.4/Documentation/devicetree/bindings/iommu/
Darm,smmu.yaml26 - description: Qcom SoCs implementing "arm,smmu-v2"
35 - description: Qcom SoCs implementing "qcom,smmu-500" and "arm,mmu-500"
69 - description: Qcom SoCs implementing "arm,mmu-500" (legacy binding)
88 - description: Qcom Adreno GPUs implementing "qcom,smmu-500" and "arm,mmu-500"
112 - description: Qcom Adreno GPUs implementing "arm,mmu-500" (legacy binding)
122 - description: Qcom Adreno GPUs implementing "arm,smmu-v2"
138 - description: Marvell SoCs implementing "arm,mmu-500"
/linux-6.14.4/rust/macros/
Dpinned_drop.rs10 // Ensure that we are implementing `PinnedDrop`. in pinned_drop()
36 .unwrap_or_else(|| panic!("Expected an `impl` block implementing `PinnedDrop`.")); in pinned_drop()
/linux-6.14.4/Documentation/userspace-api/media/v4l/
Dvidioc-encoder-cmd.rst106 For a device implementing the :ref:`encoder`, once the drain sequence
118 For a device implementing the :ref:`encoder`, the command will initiate
160 A drain sequence of a device implementing the :ref:`encoder` is still in
Dvidioc-decoder-cmd.rst153 For a device implementing the :ref:`decoder`, once the drain sequence
173 For a device implementing the :ref:`decoder`, the command will initiate
209 A drain sequence of a device implementing the :ref:`decoder` is still in
Dextended-controls.rst15 be a very useful model for implementing more complicated driver APIs
19 implementing this extended control mechanism: the MPEG standard is quite
/linux-6.14.4/Documentation/driver-api/
Dpwm.rst8 cell phones. PWMs with a fixed purpose have no need implementing
137 Implementing a PWM driver
153 When implementing polarity support in a PWM driver, make sure to respect the
/linux-6.14.4/arch/powerpc/sysdev/
Dfsl_rmu.c515 * @mport: Master port implementing the port write unit
536 * @mport: Master port implementing the port write unit
710 * @mport: Master port implementing the outbound message unit
817 * @mport: Master port implementing the outbound message unit
842 * @mport: Master port implementing the inbound message unit
918 * @mport: Master port implementing the inbound message unit
942 * @mport: Master port implementing the inbound message unit
975 * @mport: Master port implementing the inbound message unit
1021 * @mport: Master port implementing the inbound doorbell unit
/linux-6.14.4/Documentation/bpf/
Dbpf_licensing.rst29 Using the eBPF instruction set requires implementing code in both kernel space
53 in HW or via the use of implementing firmware with a proprietary license.
/linux-6.14.4/rust/kernel/block/
Dmq.rs3 //! This module provides types for implementing block drivers that interface the
40 //! This can be useful when implementing drivers where one piece of hardware
/linux-6.14.4/Documentation/driver-api/iio/
Dbuffers.rst74 For implementing buffer support a driver should initialize the following
90 The driver implementing the accelerometer described above will have the
/linux-6.14.4/include/linux/
Dgpio.h9 * If you're implementing a GPIO driver, only include <linux/gpio/driver.h>
10 * If you're implementing a GPIO consumer, only include <linux/gpio/consumer.h>
/linux-6.14.4/drivers/pmdomain/ti/
DKconfig15 Generic power domain implementation for TI device implementing
/linux-6.14.4/drivers/iommu/riscv/
DKconfig14 Say Y here if your SoC includes an IOMMU device implementing
/linux-6.14.4/drivers/iio/magnetometer/
DKconfig85 This driver is only implementing magnetometer part, which has
102 This driver is only implementing magnetometer part, which has
/linux-6.14.4/Documentation/devicetree/bindings/interrupt-controller/
Dsnps,archs-intc.txt1 * ARC-HS incore Interrupt Controller (Provided by cores implementing ARCv2 ISA)
/linux-6.14.4/net/mac802154/
DKconfig13 networking stack for SoftMAC devices (the ones implementing
/linux-6.14.4/Documentation/devicetree/bindings/sound/
Dcomponent-common.yaml16 Card implementing the routing property define the connection between
/linux-6.14.4/Documentation/networking/
Dsriov.rst7 Modern NICs are strongly encouraged to focus on implementing the ``switchdev``
/linux-6.14.4/Documentation/devicetree/bindings/firmware/
Darm,scpi.yaml14 Firmware implementing the SCPI described in ARM document number ARM DUI
18 This binding is intended to define the interface the firmware implementing
/linux-6.14.4/Documentation/hwmon/
Dscpi-hwmon.rst18 System Control Processor (SCP) implementing the System Control
/linux-6.14.4/Documentation/filesystems/
Dbtrfs.rst7 Btrfs is a copy on write filesystem for Linux aimed at implementing advanced

12345678910>>...21