Home
last modified time | relevance | path

Searched refs:follow (Results 1 – 25 of 366) sorted by relevance

12345678910>>...15

/linux/Documentation/devicetree/bindings/regulator/
A Dqcom,spmi-regulator.yaml64 BIT(0) = follow HW0_EN signal
65 BIT(1) = follow HW1_EN signal
66 BIT(2) = follow HW2_EN signal
67 BIT(3) = follow HW3_EN signal
78 BIT(0) = follow HW0_EN signal
79 BIT(1) = follow HW1_EN signal
80 BIT(2) = follow HW2_EN signal
81 BIT(3) = follow HW3_EN signal
82 BIT(4) = follow PMIC awake state
/linux/Documentation/devicetree/bindings/mfd/
A Dcanaan,k210-sysctl.yaml42 should follow the bindings specified in
51 should follow the bindings specified in
60 should follow the bindings specified in
A Dbrcm,bcm6358-gpio-sysctl.yaml41 should follow the bindings specified in
50 should follow the bindings specified in
A Dbrcm,bcm6328-gpio-sysctl.yaml41 should follow the bindings specified in
50 should follow the bindings specified in
A Dbrcm,bcm6318-gpio-sysctl.yaml41 should follow the bindings specified in
50 should follow the bindings specified in
A Dbrcm,bcm63268-gpio-sysctl.yaml41 should follow the bindings specified in
50 should follow the bindings specified in
A Dbrcm,bcm6362-gpio-sysctl.yaml41 should follow the bindings specified in
50 should follow the bindings specified in
A Dbrcm,bcm6368-gpio-sysctl.yaml41 should follow the bindings specified in
50 should follow the bindings specified in
/linux/fs/btrfs/
A Dprint-tree.h16 void btrfs_print_tree(const struct extent_buffer *c, bool follow);
A Dprint-tree.c389 void btrfs_print_tree(const struct extent_buffer *c, bool follow) in btrfs_print_tree() argument
418 if (!follow) in btrfs_print_tree()
444 btrfs_print_tree(next, follow); in btrfs_print_tree()
/linux/scripts/
A Ddev-needs.sh40 --exclude-devlinks Don't follow device links when tracking probe
125 # They can also have cycles. So, don't follow them.
/linux/tools/testing/selftests/lkdtm/
A Dstack-entropy.sh24 dmesg --follow >"$log" & pid=$!
/linux/Documentation/bpf/
A Dfs_kfuncs.rst16 To avoid recursions, these kfuncs follow the following rules:
/linux/Documentation/userspace-api/media/v4l/
A Dvidioc-g-dv-timings.rst231 - The timings follow the CEA-861 Digital TV Profile standard
233 - The timings follow the VESA Discrete Monitor Timings standard
235 - The timings follow the VESA Coordinated Video Timings standard
237 - The timings follow the VESA Generalized Timings Formula standard
239 - The timings follow the SDI Timings standard.
/linux/fs/coda/
A Dpioctl.c69 data.follow ? LOOKUP_FOLLOW : 0, &path); in coda_pioctl()
/linux/Documentation/firmware-guide/acpi/
A DDSD-properties-rules.rst52 Valid property sets must follow the guidance given by the Device Properties UUID
59 return property sets which do not follow that rule from _DSD in data packages
85 It often is useful to make _DSD return property sets that follow Device Tree
/linux/Documentation/devicetree/bindings/mtd/partitions/
A Dbrcm,bcm963xx-cfe-nor-partitions.txt4 Most Broadcom BCM63XX SoC based devices follow the Broadcom reference layout for
/linux/drivers/misc/ocxl/
A DKconfig29 dedicated OpenCAPI link, and don't follow the same protocol.
/linux/Documentation/process/
A Dmaintainer-soc-clean-dts.rst10 SoC platforms or subarchitectures should follow all the rules from
/linux/Documentation/
A DKconfig18 The files under Documentation/ABI should follow what's
/linux/Documentation/i2c/
A Dslave-eeprom-backend.rst14 'slave-<type>[ro]'. Examples follow:
/linux/Documentation/devicetree/bindings/thermal/
A Darmada-thermal.txt15 follow the rules described in:
/linux/Documentation/admin-guide/
A Dedid.rst11 either correctly working because all components follow the standards -
/linux/Documentation/devicetree/bindings/mmc/
A Dmmc-spi-slot.yaml46 For historical reasons, this does not follow the generic mmc-controller
/linux/Documentation/ABI/testing/
A Dsysfs-platform-eeepc-laptop43 is defined as follow::

Completed in 36 milliseconds

12345678910>>...15