Searched refs:follow (Results 1 – 25 of 302) sorted by relevance
12345678910>>...13
| /Linux-v5.10/Documentation/devicetree/bindings/power/reset/ |
| D | qcom,pon.txt | 17 -pwrkey: Specifies the subnode pwrkey and should follow the
19 -resin: Specifies the subnode resin and should follow the
22 The rest of the properties should follow the generic reboot-mode description
|
| D | nvmem-reboot-mode.txt | 13 The rest of the properties should follow the generic reboot-mode description
|
| /Linux-v5.10/Documentation/devicetree/bindings/regulator/ |
| D | qcom,spmi-regulator.txt | 259 BIT(0) = follow HW0_EN signal
260 BIT(1) = follow HW1_EN signal
261 BIT(2) = follow HW2_EN signal
262 BIT(3) = follow HW3_EN signal
271 BIT(0) = follow HW0_EN signal
272 BIT(1) = follow HW1_EN signal
273 BIT(2) = follow HW2_EN signal
274 BIT(3) = follow HW3_EN signal
275 BIT(4) = follow PMIC awake state
|
| /Linux-v5.10/fs/btrfs/ |
| D | print-tree.h | 13 void btrfs_print_tree(struct extent_buffer *c, bool follow);
|
| D | print-tree.c | 364 void btrfs_print_tree(struct extent_buffer *c, bool follow) in btrfs_print_tree() argument
393 if (!follow) in btrfs_print_tree()
416 btrfs_print_tree(next, follow); in btrfs_print_tree()
|
| /Linux-v5.10/scripts/ |
| D | dev-needs.sh | 40 --exclude-devlinks Don't follow device links when tracking probe
125 # They can also have cycles. So, don't follow them.
|
| /Linux-v5.10/Documentation/networking/ |
| D | nf_flowtable.rst | 13 Initial packets follow the classic forwarding path, once the flow enters the
31 follow the classic forwarding path unless the user explicitly instruct packets
72 neigh_xmit(). Fragmented traffic is passed up to follow the classic forwarding
|
| /Linux-v5.10/Documentation/devicetree/bindings/power/ |
| D | xlnx,zynqmp-genpd.txt | 4 The binding for zynqmp-power-controller follow the common
|
| /Linux-v5.10/fs/coda/ |
| D | pioctl.c | 67 data.follow ? LOOKUP_FOLLOW : 0, &path); in coda_pioctl()
|
| /Linux-v5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-dv-timings.rst | 227 - The timings follow the CEA-861 Digital TV Profile standard
229 - The timings follow the VESA Discrete Monitor Timings standard
231 - The timings follow the VESA Coordinated Video Timings standard
233 - The timings follow the VESA Generalized Timings Formula standard
235 - The timings follow the SDI Timings standard.
|
| /Linux-v5.10/Documentation/firmware-guide/acpi/ |
| D | DSD-properties-rules.rst | 48 Valid property sets must follow the guidance given by the Device Properties UUID
55 return property sets which do not follow that rule from _DSD in data packages
81 It often is useful to make _DSD return property sets that follow Device Tree
|
| /Linux-v5.10/Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm963xx-cfe-nor-partitions.txt | 4 Most Broadcom BCM63XX SoC based devices follow the Broadcom reference layout for
|
| /Linux-v5.10/Documentation/devicetree/bindings/mmc/ |
| D | mmc-spi-slot.txt | 14 Write-Protect GPIO. Note that this does not follow the
|
| /Linux-v5.10/Documentation/devicetree/bindings/spi/ |
| D | adi,axi-spi-engine.txt | 16 master. They follow the generic SPI bindings as outlined in spi-bus.txt.
|
| /Linux-v5.10/Documentation/ |
| D | Kconfig | 17 The files under Documentation/ABI should follow what's
|
| /Linux-v5.10/drivers/misc/ocxl/ |
| D | Kconfig | 29 dedicated OpenCAPI link, and don't follow the same protocol.
|
| /Linux-v5.10/Documentation/devicetree/bindings/i3c/ |
| D | snps,dw-i3c-master.txt | 23 I3C device connected on the bus follow the generic description (see
|
| D | cdns,i3c-master.txt | 24 I3C device connected on the bus follow the generic description (see
|
| /Linux-v5.10/Documentation/i2c/ |
| D | slave-eeprom-backend.rst | 14 'slave-<type>[ro]'. Examples follow:
|
| /Linux-v5.10/Documentation/userspace-api/media/dvb/ |
| D | audio-set-id.rst | 49 AC3 and in [0xA0,0xA7] for LPCM. More specifications may follow for
|
| /Linux-v5.10/Documentation/devicetree/bindings/thermal/ |
| D | armada-thermal.txt | 14 follow the rules described in:
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-platform-eeepc-laptop | 43 is defined as follow::
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | gfs2-uevents.rst | 19 is successful, an ONLINE uevent will follow. If it is not successful
20 then a REMOVE uevent will follow.
|
| /Linux-v5.10/Documentation/cdrom/ |
| D | packet-writing.rst | 58 However, some drives don't follow the specification and expect the
60 follow the specification, but suffer bad performance problems if the
|
| /Linux-v5.10/drivers/staging/media/ |
| D | Kconfig | 8 Most of them don't follow properly the V4L, DVB and/or RC API's,
|
12345678910>>...13
