Home
last modified time | relevance | path

Searched full:having (Results 1 – 25 of 413) sorted by relevance

12345678910>>...17

/Documentation/admin-guide/LSM/
DLoadPin.rst19 created to toggle pinning: ``/proc/sys/kernel/loadpin/enabled``. (Having
20 a mutable filesystem means pinning is mutable too, but having the
/Documentation/ABI/stable/
Dsysfs-bus-mhi8 without having the device power on at least once, the file will
19 read without having the device power on at least once, the file
/Documentation/admin-guide/device-mapper/
Ddm-service-time.rst30 other paths having a positive value are available.
51 Basically, dm-service-time selects a path having minimum service time
71 If calculated service time is equal, the path having maximum
/Documentation/devicetree/bindings/soc/fsl/cpm_qe/
Dgpio.txt17 - fsl,cpm1-gpio-irq-mask : For banks having interrupt capability (like port C
20 - interrupts : This property provides the list of interrupt for each GPIO having
/Documentation/devicetree/bindings/clock/
Dpxa-clock.txt7 The clock consumer should specify the desired clock by having the clock
Dclps711x-clock.txt9 The clock consumer should specify the desired clock by having the clock
Darmada3700-tbg-clock.txt6 The TBG clock consumer should specify the desired clock by having the
Dlsi,axm5516-clks.txt9 The consumer specifies the desired clock by having the clock ID in its "clocks"
Dimx21-clock.yaml13 The clock consumer should specify the desired clock by having the clock
Dimx1-clock.yaml13 The clock consumer should specify the desired clock by having the clock
Dimx27-clock.yaml13 The clock consumer should specify the desired clock by having the clock
Dvf610-clock.txt21 The clock consumer should specify the desired clock by having the clock
Dfsl,scu-clk.yaml16 The clock consumer should specify the desired clock by having the clock
Dnxp,imx95-blk-ctl.yaml35 The clock consumer should specify the desired clock by having the clock
Dimx23-clock.yaml13 The clock consumer should specify the desired clock by having the clock
/Documentation/devicetree/bindings/ata/
Dbaikal,bt1-ahci.yaml60 Due to having AXI3 bus interface utilized the maximum Tx DMA
67 Due to having AXI3 bus interface utilized the maximum Rx DMA
/Documentation/usb/
Draw-gadget.rst35 having multiple Raw Gadget instances bound to different UDCs.
78 fuzzing by having a single syscall fully process a single USB request. This
/Documentation/devicetree/bindings/mfd/
Dkhadas,mcu.yaml22 "#cooling-cells": # Only needed for boards having FAN control feature
/Documentation/devicetree/bindings/leds/
Dleds-ns2.txt13 should be given in order to avoid having an unknown mode at driver probe time.
/Documentation/ABI/testing/
Dsysfs-bus-acpi27 This file is present for device objects having the _HID
43 objects representing devices having standard enumeration
/Documentation/driver-api/firmware/
Dbuilt-in-fw.rst6 into vmlinux directly, to enable avoiding having to look for firmware from
/Documentation/devicetree/bindings/net/
Dqca,qca808x.yaml15 2 LEDs have dedicated pins with the 3rd LED having the
/Documentation/devicetree/bindings/iommu/
Dpkvm,pviommu.yaml37 devices having the same ID are part of the same group.
/Documentation/devicetree/
Ddynamic-resolution-notes.rst14 proper dtc option and having a /plugin/ tag. This generates the
/Documentation/devicetree/bindings/mailbox/
Damlogic,meson-gxbb-mhu.yaml19 STAT register and the remote clears it after having read the data.

12345678910>>...17