summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/power
diff options
context:
space:
mode:
authorOlof Johansson <olof@lixom.net>2021-06-15 18:10:12 +0300
committerOlof Johansson <olof@lixom.net>2021-06-15 18:10:13 +0300
commitbb1a7fcec17eea1d60678f1540aa2226eef9d70a (patch)
tree6d1b65e5661cf09d383aebb41bdded1fd590d5f9 /Documentation/devicetree/bindings/power
parent406b968552c6bad8d8c8488e910459652732cc07 (diff)
parentcd044eafd7105275220f6b7140a8a8fb64e0e5af (diff)
downloadlinux-bb1a7fcec17eea1d60678f1540aa2226eef9d70a.tar.xz
Merge tag 'imx-bindings-5.14' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into arm/dt
i.MX dt-bindings update for 5.14: - Add vendor prefixes for congatec GmbH and DaSheng, Inc. - Add compatibles for i.MX6Q DaSheng COM-9XX SBC, GE B1x5pv2 and i.MX8MM GW7901 boards. - Add an optional 'resets' property for i.MX GPCv2 bindings. * tag 'imx-bindings-5.14' of git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux: dt-bindings: arm: fsl: add GE B1x5pv2 boards dt-bindings: vendor-prefixes: add congatec dt-bindings: imx: gpcv2: add support for optional resets dt-bindings: arm: imx: Add i.mx6q DaSheng COM-9XX SBC dt-bindings: add dasheng vendor prefix dt-bindings: arm: imx: add imx8mm gw7901 support Link: https://lore.kernel.org/r/20210613082544.16067-3-shawnguo@kernel.org Signed-off-by: Olof Johansson <olof@lixom.net>
Diffstat (limited to 'Documentation/devicetree/bindings/power')
-rw-r--r--Documentation/devicetree/bindings/power/fsl,imx-gpcv2.yaml10
1 files changed, 10 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/power/fsl,imx-gpcv2.yaml b/Documentation/devicetree/bindings/power/fsl,imx-gpcv2.yaml
index a96e6dbf1858..eb248f24dce6 100644
--- a/Documentation/devicetree/bindings/power/fsl,imx-gpcv2.yaml
+++ b/Documentation/devicetree/bindings/power/fsl,imx-gpcv2.yaml
@@ -66,6 +66,16 @@ properties:
power-supply: true
+ resets:
+ description: |
+ A number of phandles to resets that need to be asserted during
+ power-up sequencing of the domain. The resets belong to devices
+ located inside the power domain, which need to be held in reset
+ across the power-up sequence. So no means to specify what each
+ reset is in a generic power-domain binding.
+ minItems: 1
+ maxItems: 4
+
required:
- '#power-domain-cells'
- reg