Searched full:follow (Results 1 – 25 of 267) sorted by relevance
1234567891011
| /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
|
| /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
|
| /Documentation/admin-guide/ |
| D | reporting-bugs.rst | 139 Follow up
145 Linux kernel maintainers expect bug reporters to be able to follow up on
149 never follow up on a request to try out a fix.
152 on a supported kernel, even if you can't follow up with retests. Follow
|
| /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
|
| /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
|
| /Documentation/ |
| D | Kconfig | 17 The files under Documentation/ABI should follow what's
|
| /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.
|
| D | dev-encoder.rst | 164 follow standard semantics.
190 follow standard semantics.
199 follow standard semantics.
216 follow standard semantics.
226 follow standard semantics.
388 follow standard semantics.
421 follow standard semantics.
548 configuration change to be allowed. To do this, it may follow the `Drain`
560 related ``CAPTURE`` buffers are given to the client, the client must follow the
|
| /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
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-spi-slot.txt | 14 Write-Protect GPIO. Note that this does not follow the
|
| /Documentation/process/ |
| D | code-of-conduct-interpretation.rst | 97 or bug tracking tools should follow the guidelines of the Code of
100 performed using a kernel.org email account must follow the Code of
102 corporate email account must follow the specific rules of that
|
| /Documentation/sphinx/ |
| D | parallel-wrapper.sh | 4 # Figure out if we should follow a specific parallelism from the make
|
| /Documentation/devicetree/bindings/spi/ |
| D | adi,axi-spi-engine.txt | 16 master. They follow the generic SPI bindings as outlined in spi-bus.txt.
|
| /Documentation/devicetree/bindings/power/ |
| D | xlnx,zynqmp-genpd.txt | 4 The binding for zynqmp-power-controller follow the common
|
| /Documentation/devicetree/bindings/thermal/ |
| D | armada-thermal.txt | 14 follow the rules described in:
|
| /Documentation/i2c/ |
| D | slave-eeprom-backend.rst | 14 'slave-<type>[ro]'. Examples follow:
|
| /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.
|
| /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
|
| /Documentation/userspace-api/media/dvb/ |
| D | audio-set-id.rst | 49 AC3 and in [0xA0,0xA7] for LPCM. More specifications may follow for
|
| /Documentation/hwmon/ |
| D | lm77.rst | 35 * When setting a limit, its hysteresis will automatically follow, the
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-eeepc-laptop | 43 is defined as follow::
|
| /Documentation/virt/kvm/ |
| D | review-checklist.rst | 7 1. The patch must follow Documentation/process/coding-style.rst and
|
| /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
|
1234567891011