Searched full:follow (Results 1 – 25 of 252) 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
|
| D | syscon-reboot-mode.txt | 19 The rest of the properties should follow the generic reboot-mode description
|
| /Documentation/devicetree/bindings/regulator/ |
| D | qcom,spmi-regulator.txt | 203 BIT(0) = follow HW0_EN signal
204 BIT(1) = follow HW1_EN signal
205 BIT(2) = follow HW2_EN signal
206 BIT(3) = follow HW3_EN signal
215 BIT(0) = follow HW0_EN signal
216 BIT(1) = follow HW1_EN signal
217 BIT(2) = follow HW2_EN signal
218 BIT(3) = follow HW3_EN signal
219 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.txt | 10 Initial packets follow the classic forwarding path, once the flow enters the
28 follow the classic forwarding path unless the user explicitly instruct packets
67 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/media/uapi/v4l/ |
| D | vidioc-g-dv-timings.rst | 230 - The timings follow the CEA-861 Digital TV Profile standard
232 - The timings follow the VESA Discrete Monitor Timings standard
234 - The timings follow the VESA Coordinated Video Timings standard
236 - The timings follow the VESA Generalized Timings Formula standard
238 - The timings follow the SDI Timings standard.
|
| /Documentation/devicetree/bindings/arm/ti/ |
| D | k3.txt | 5 shall follow the following scheme:
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-spi-slot.txt | 14 Write-Protect GPIO. Note that this does not follow the
|
| /Documentation/devicetree/bindings/sram/ |
| D | rockchip-smp-sram.txt | 14 The rest of the properties should follow the generic mmio-sram discription
|
| D | samsung-sram.txt | 17 The rest of the properties should follow the generic mmio-sram discription
|
| /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/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
|
| D | stable-kernel-rules.rst | 29 - It must follow the
38 - If the patch covers files in net/ or drivers/net please follow netdev stable
45 process but should follow the procedures in
|
| /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/filesystems/ |
| D | gfs2-uevents.txt | 15 is successful, an ONLINE uevent will follow. If it is not successful
16 then a REMOVE uevent will follow.
|
| /Documentation/devicetree/bindings/arm/amlogic/ |
| D | smp-sram.txt | 16 The rest of the properties should follow the generic mmio-sram discription
|
| /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/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/hwmon/ |
| D | lm77.rst | 35 * When setting a limit, its hysteresis will automatically follow, the
|
| /Documentation/virt/kvm/ |
| D | review-checklist.txt | 4 1. The patch must follow Documentation/process/coding-style.rst and
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-eeepc-laptop | 39 is defined as follow:
|
1234567891011