dt-bindings: power: Convert Generic Power Domain bindings to json-schema
Subsystems (23)
Krzysztof Kozlowski
maintainerRFC 1/2 dt-bindings: power: Convert Generic Power Domain bindings to json-schema
Convert Generic Power Domain bindings to DT schema format using json-schema. The consumer bindings are split to separate file.
---
TODO:
1. How the consumer bindings should match nodes?
2. Somehow the example complains:Documentation/devicetree/bindings/power/power-domain.example.dt.yaml: power-controller@12341000: power-domains:0: [1, 0] is too long Documentation/devicetree/bindings/power/power-domain.example.dt.yaml: power-controller@12341000: power-domains:0:1: missing phandle tag in 0
3. Current matching by node name causes false positives:arch/arm/boot/dts/am335x-icev2.dt.yaml: power-controller@2d: '#power-domain-cells' is a required property arch/arm/boot/dts/qcom-apq8064-cm-qs600.dt.yaml: power-controller@2099000: '#power-domain-cells' is a required property
--- .../devicetree/bindings/arm/arm,scmi.txt | 2 +- .../devicetree/bindings/arm/arm,scpi.txt | 2 +- .../bindings/arm/freescale/fsl,scu.txt | 2 +- .../bindings/clock/clk-exynos-audss.txt | 2 +- .../bindings/clock/exynos5433-clock.txt | 4 +- .../bindings/clock/renesas,cpg-mssr.txt | 2 +- .../clock/renesas,r8a7778-cpg-clocks.txt | 2 +- .../clock/renesas,r8a7779-cpg-clocks.txt | 2 +- .../clock/renesas,rcar-gen2-cpg-clocks.txt | 2 +- .../bindings/clock/renesas,rz-cpg-clocks.txt | 2 +- .../bindings/clock/ti/davinci/psc.txt | 2 +- .../bindings/display/etnaviv/etnaviv-drm.txt | 2 +- .../devicetree/bindings/display/msm/dpu.txt | 2 +- .../devicetree/bindings/display/msm/mdp5.txt | 2 +- .../devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- .../firmware/nvidia,tegra186-bpmp.txt | 2 +- .../bindings/media/imx7-mipi-csi2.txt | 3 +- .../bindings/media/mediatek-jpeg-decoder.txt | 3 +- .../bindings/media/mediatek-mdp.txt | 3 +- .../bindings/opp/qcom-nvmem-cpufreq.txt | 2 +- .../devicetree/bindings/pci/pci-keystone.txt | 2 +- .../bindings/phy/ti,phy-am654-serdes.txt | 2 +- .../bindings/power/amlogic,meson-gx-pwrc.txt | 2 +- .../devicetree/bindings/power/fsl,imx-gpc.txt | 2 +- .../bindings/power/fsl,imx-gpcv2.txt | 2 +- .../power/power-domain-consumers.yaml | 124 +++++++++++ .../bindings/power/power-domain.yaml | 136 ++++++++++++ .../bindings/power/power_domain.txt | 205 ------------------ .../devicetree/bindings/power/qcom,rpmpd.txt | 2 +- .../bindings/power/renesas,rcar-sysc.txt | 2 +- .../bindings/power/renesas,sysc-rmobile.txt | 2 +- .../bindings/power/xlnx,zynqmp-genpd.txt | 2 +- .../bindings/soc/bcm/brcm,bcm2835-pm.txt | 2 +- .../bindings/soc/mediatek/scpsys.txt | 2 +- .../bindings/soc/ti/sci-pm-domain.txt | 2 +- .../bindings/usb/nvidia,tegra124-xusb.txt | 4 +- MAINTAINERS | 2 +- 37 files changed, 299 insertions(+), 241 deletions(-) create mode 100644 Documentation/devicetree/bindings/power/power-domain-consumers.yaml create mode 100644 Documentation/devicetree/bindings/power/power-domain.yaml delete mode 100644 Documentation/devicetree/bindings/power/power_domain.txt
Documentation/devicetree/bindings/arm/arm,scmi.txt +1 -1
@@ -100,7 +100,7 @@ Required sub-node properties: [0] http://infocenter.arm.com/help/topic/com.arm.doc.den0056a/index.html [1] Documentation/devicetree/bindings/clock/clock-bindings.txt -[2] Documentation/devicetree/bindings/power/power_domain.txt +[2] Documentation/devicetree/bindings/power/power-domain.yaml [3] Documentation/devicetree/bindings/thermal/thermal.txt [4] Documentation/devicetree/bindings/sram/sram.txt [5] Documentation/devicetree/bindings/reset/reset.txt
Documentation/devicetree/bindings/arm/arm,scpi.txt +1 -1
@@ -110,7 +110,7 @@ Required properties: [1] Documentation/devicetree/bindings/clock/clock-bindings.txt [2] Documentation/devicetree/bindings/thermal/thermal.txt [3] Documentation/devicetree/bindings/sram/sram.txt -[4] Documentation/devicetree/bindings/power/power_domain.txt +[4] Documentation/devicetree/bindings/power/power-domain.yaml Example:
Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt +1 -1
@@ -124,7 +124,7 @@ Required properties for Pinctrl sub nodes: CONFIG settings. [1] Documentation/devicetree/bindings/clock/clock-bindings.txt -[2] Documentation/devicetree/bindings/power/power_domain.txt +[2] Documentation/devicetree/bindings/power/power-domain.yaml [3] Documentation/devicetree/bindings/pinctrl/fsl,imx-pinctrl.txt RTC bindings based on SCU Message Protocol
Documentation/devicetree/bindings/clock/clk-exynos-audss.txt +1 -1
@@ -36,7 +36,7 @@ Required Properties: Optional Properties: - power-domains: a phandle to respective power domain node as described by - generic PM domain bindings (see power/power_domain.txt for more + generic PM domain bindings (see power/power-domain-consumers.yaml for more information). The following is the list of clocks generated by the controller. Each clock is
Documentation/devicetree/bindings/clock/exynos5433-clock.txt +2 -2
@@ -178,8 +178,8 @@ Required Properties: Optional properties: - power-domains: a phandle to respective power domain node as described by - generic PM domain bindings (see power/power_domain.txt for more - information). + generic PM domain bindings (see power/power-domain-consumers.yaml + for more information). Each clock is assigned an identifier and client nodes can use this identifier to specify the clock which they consume.
Documentation/devicetree/bindings/clock/renesas,cpg-mssr.txt +1 -1
@@ -59,7 +59,7 @@ Required Properties: power-managed through Module Standby should refer to the CPG device node in their "power-domains" property, as documented by the generic PM Domain bindings in - Documentation/devicetree/bindings/power/power_domain.txt. + Documentation/devicetree/bindings/power/power-domain.yaml. - #reset-cells: Must be 1 - The single reset specifier cell must be the module number, as defined
Documentation/devicetree/bindings/clock/renesas,r8a7778-cpg-clocks.txt +1 -1
@@ -17,7 +17,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain-consumers.yaml. Examples
Documentation/devicetree/bindings/clock/renesas,r8a7779-cpg-clocks.txt +1 -1
@@ -19,7 +19,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain-consumers.yaml. Examples
Documentation/devicetree/bindings/clock/renesas,rcar-gen2-cpg-clocks.txt +1 -1
@@ -28,7 +28,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain-consumers.yaml. Examples
Documentation/devicetree/bindings/clock/renesas,rz-cpg-clocks.txt +1 -1
@@ -21,7 +21,7 @@ Required Properties: SoC devices that are part of the CPG/MSTP Clock Domain and can be power-managed through an MSTP clock should refer to the CPG device node in their "power-domains" property, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain-consumers.yaml. Examples
Documentation/devicetree/bindings/clock/ti/davinci/psc.txt +1 -1
@@ -67,5 +67,5 @@ Examples: Also see: - Documentation/devicetree/bindings/clock/clock-bindings.txt -- Documentation/devicetree/bindings/power/power_domain.txt +- Documentation/devicetree/bindings/power/power-domain.yaml - Documentation/devicetree/bindings/reset/reset.txt
Documentation/devicetree/bindings/display/etnaviv/etnaviv-drm.txt +1 -1
@@ -20,7 +20,7 @@ Required properties: Optional properties: - power-domains: a power domain consumer specifier according to - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain-consumers.yaml example:
Documentation/devicetree/bindings/display/msm/dpu.txt +1 -1
@@ -13,7 +13,7 @@ Required properties: - reg-names: register region names. The following region is required: * "mdss" - power-domains: a power domain consumer specifier according to - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain-consumers.yaml - clocks: list of clock specifiers for clocks needed by the device. - clock-names: device clock names, must be in same order as clocks property. The following clocks are required:
Documentation/devicetree/bindings/display/msm/mdp5.txt +1 -1
@@ -19,7 +19,7 @@ Required properties: - #interrupt-cells: specifies the number of cells needed to encode an interrupt source, should be 1. - power-domains: a power domain consumer specifier according to - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain-consumers.yaml - clocks: device clocks. See ../clocks/clock-bindings.txt for details. - clock-names: the following clocks are required. * "iface"
Documentation/devicetree/bindings/dsp/fsl,dsp.yaml +1 -1
@@ -36,7 +36,7 @@ properties: power-domains: description: List of phandle and PM domain specifier as documented in - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain-consumers.yaml maxItems: 4 mboxes:
Documentation/devicetree/bindings/firmware/nvidia,tegra186-bpmp.txt +1 -1
@@ -32,7 +32,7 @@ implemented by this node: - .../clock/clock-bindings.txt - <dt-bindings/clock/tegra186-clock.h> -- ../power/power_domain.txt +- ../power/power-domain.yaml - <dt-bindings/power/tegra186-powergate.h> - .../reset/reset.txt - <dt-bindings/reset/tegra186-reset.h>
Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt +2 -1
@@ -17,7 +17,8 @@ Required properties: - clock-names : must contain "pclk", "wrap" and "phy" entries, matching entries in the clock property; - power-domains : a phandle to the power domain, see - Documentation/devicetree/bindings/power/power_domain.txt for details. + Documentation/devicetree/bindings/power/power-domain-consumers.yaml + for details. - reset-names : should include following entry "mrst"; - resets : a list of phandle, should contain reset entry of reset-names;
Documentation/devicetree/bindings/media/mediatek-jpeg-decoder.txt +2 -1
@@ -14,7 +14,8 @@ Required properties: Documentation/devicetree/bindings/clock/clock-bindings.txt for details. - clock-names: must contain "jpgdec-smi" and "jpgdec". - power-domains: a phandle to the power domain, see - Documentation/devicetree/bindings/power/power_domain.txt for details. + Documentation/devicetree/bindings/power/power-domain-consumers.yaml + for details. - mediatek,larb: must contain the local arbiters in the current Socs, see Documentation/devicetree/bindings/memory-controllers/mediatek,smi-larb.txt for details.
Documentation/devicetree/bindings/media/mediatek-mdp.txt +2 -1
@@ -17,7 +17,8 @@ Required properties (all function blocks, child node): - clocks: device clocks, see Documentation/devicetree/bindings/clock/clock-bindings.txt for details. - power-domains: a phandle to the power domain, see - Documentation/devicetree/bindings/power/power_domain.txt for details. + Documentation/devicetree/bindings/power/power-domain-consumers.yaml + for details. Required properties (DMA function blocks, child node): - compatible: Should be one of
Documentation/devicetree/bindings/opp/qcom-nvmem-cpufreq.txt +1 -1
@@ -27,7 +27,7 @@ In 'cpu' nodes: - power-domains: A phandle pointing to the PM domain specifier which provides the performance states available for active state management. Please refer to the power-domains bindings - Documentation/devicetree/bindings/power/power_domain.txt + Documentation/devicetree/bindings/power/power-domain-consumers.yaml and also examples below. - power-domain-names: Should be - 'cpr' for qcs404.
Documentation/devicetree/bindings/pci/pci-keystone.txt +1 -1
@@ -88,7 +88,7 @@ num-ob-windows: As specified in num-lanes: As specified in Documentation/devicetree/bindings/pci/designware-pcie.txt power-domains: As documented by the generic PM domain bindings in - Documentation/devicetree/bindings/power/power_domain.txt. + Documentation/devicetree/bindings/power/power-domain-consumers.yaml. ti,syscon-pcie-mode: phandle to the device control module required to configure PCI in either RC mode or EP mode.
Documentation/devicetree/bindings/phy/ti,phy-am654-serdes.txt +1 -1
@@ -17,7 +17,7 @@ Required properties: 1 - PCIe0 Lane1 2 - ICSS2 SGMII Lane1 - power-domains: As documented by the generic PM domain bindings in - Documentation/devicetree/bindings/power/power_domain.txt. + Documentation/devicetree/bindings/power/power-domain-consumers.yaml. - clocks: List of clock-specifiers representing the input to the SERDES. Should have 3 items representing the left input clock, external reference clock and right input clock in that order.
Documentation/devicetree/bindings/power/amlogic,meson-gx-pwrc.txt +1 -1
@@ -10,7 +10,7 @@ The Video Processing Unit power domain is controlled by this power controller, but the domain requires some external resources to meet the correct power sequences. The bindings must respect the power domain bindings as described in the file -power_domain.txt +power-domain.yaml Device Tree Bindings: ---------------------
Documentation/devicetree/bindings/power/fsl,imx-gpc.txt +1 -1
@@ -19,7 +19,7 @@ Required properties: - ipg The power domains are generic power domain providers as documented in -Documentation/devicetree/bindings/power/power_domain.txt. They are described as +Documentation/devicetree/bindings/power/power-domain.yaml. They are described as subnodes of the power gating controller 'pgc' node of the GPC and should contain the following:
Documentation/devicetree/bindings/power/fsl,imx-gpcv2.txt +1 -1
@@ -17,7 +17,7 @@ Required properties: Power domains contained within GPC node are generic power domain providers, documented in -Documentation/devicetree/bindings/power/power_domain.txt, which are +Documentation/devicetree/bindings/power/power-domain.yaml, which are described as subnodes of the power gating controller 'pgc' node, which, in turn, is expected to contain the following:
Documentation/devicetree/bindings/power/power-domain-consumers.yaml new file +124 -0
124 lines not on this page · raw message
Documentation/devicetree/bindings/power/power-domain.yaml new file +136 -0
136 lines not on this page · raw message
Documentation/devicetree/bindings/power/power_domain.txt deleted +0 -205
205 lines not on this page · raw message
Documentation/devicetree/bindings/power/qcom,rpmpd.txt +1 -1
@@ -12,7 +12,7 @@ Required Properties: - #power-domain-cells: number of cells in Power domain specifier must be 1. - operating-points-v2: Phandle to the OPP table for the Power domain. - Refer to Documentation/devicetree/bindings/power/power_domain.txt + Refer to Documentation/devicetree/bindings/power/power-domain-consumers.yaml and Documentation/devicetree/bindings/opp/opp.txt for more details Refer to <dt-bindings/power/qcom-rpmpd.h> for the level values for
Documentation/devicetree/bindings/power/renesas,rcar-sysc.txt +1 -1
@@ -43,7 +43,7 @@ Example: Devices residing in a power area must refer to that power area, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain-consumers.yaml. Required properties: - power-domains: A phandle and symbolic PM domain specifier, as defined in
Documentation/devicetree/bindings/power/renesas,sysc-rmobile.txt +1 -1
@@ -29,7 +29,7 @@ Optional nodes: Each of the PM domain nodes represents a PM domain, as documented by the generic PM domain bindings in -Documentation/devicetree/bindings/power/power_domain.txt. +Documentation/devicetree/bindings/power/power-domain.yaml. The nodes should be named by the real power area names, and thus their names should be unique.
Documentation/devicetree/bindings/power/xlnx,zynqmp-genpd.txt +1 -1
@@ -4,7 +4,7 @@ Device Tree Bindings for the Xilinx Zynq MPSoC PM domains The binding for zynqmp-power-controller follow the common generic PM domain binding[1]. -[1] Documentation/devicetree/bindings/power/power_domain.txt +[1] Documentation/devicetree/bindings/power/power-domain.yaml == Zynq MPSoC Generic PM Domain Node ==
Documentation/devicetree/bindings/soc/bcm/brcm,bcm2835-pm.txt +1 -1
@@ -26,7 +26,7 @@ Optional properties: system power. This node follows the power controller bindings[3]. [1] Documentation/devicetree/bindings/reset/reset.txt -[2] Documentation/devicetree/bindings/power/power_domain.txt +[2] Documentation/devicetree/bindings/power/power-domain.yaml [3] Documentation/devicetree/bindings/power/power-controller.txt Example:
Documentation/devicetree/bindings/soc/mediatek/scpsys.txt +1 -1
@@ -8,7 +8,7 @@ The System Power Manager (SPM) inside the SCPSYS is for the MTCMOS power domain control. The driver implements the Generic PM domain bindings described in -power/power_domain.txt. It provides the power domains defined in +power/power-domain.yaml. It provides the power domains defined in - include/dt-bindings/power/mt8173-power.h - include/dt-bindings/power/mt6797-power.h - include/dt-bindings/power/mt2701-power.h
Documentation/devicetree/bindings/soc/ti/sci-pm-domain.txt +1 -1
@@ -12,7 +12,7 @@ PM Domain Node ============== The PM domain node represents the global PM domain managed by the PMMC, which in this case is the implementation as documented by the generic PM domain -bindings in Documentation/devicetree/bindings/power/power_domain.txt. Because +bindings in Documentation/devicetree/bindings/power/power-domain.yaml. Because this relies on the TI SCI protocol to communicate with the PMMC it must be a child of the pmmc node.
Documentation/devicetree/bindings/usb/nvidia,tegra124-xusb.txt +2 -2
@@ -64,12 +64,12 @@ For Tegra210: For Tegra210 and Tegra186: - power-domains: A list of PM domain specifiers that reference each power-domain used by the xHCI controller. This list must comprise of a specifier for the - XUSBA and XUSBC power-domains. See ../power/power_domain.txt and + XUSBA and XUSBC power-domains. See ../power/power-domain-consumers.yaml and ../arm/tegra/nvidia,tegra20-pmc.txt for details. - power-domain-names: A list of names that represent each of the specifiers in the 'power-domains' property. Must include 'xusb_ss' and 'xusb_host' which represent the power-domains XUSBA and XUSBC, respectively. See - ../power/power_domain.txt for details. + ../power/power-domain-consumers.yaml for details. Optional properties: --------------------
MAINTAINERS +1 -1
@@ -6869,7 +6869,7 @@ L: [email protected] S: Supported F: drivers/base/power/domain*.c F: include/linux/pm_domain.h -F: Documentation/devicetree/bindings/power/power_domain.txt +F: Documentation/devicetree/bindings/power/power-domain*.yaml GENERIC RESISTIVE TOUCHSCREEN ADC DRIVER M: Eugen Hristev <[email protected]>
Signature · 1 line
2.17.1
Krzysztof Kozlowski
maintainerRFC 2/2 dt-bindings: power: Convert Samsung Exynos Power Domain bindings to json-schema
Convert Samsung Exynos Soc Power Domain bindings to DT schema format using json-schema.
--- .../devicetree/bindings/power/pd-samsung.txt | 45 ------------ .../devicetree/bindings/power/pd-samsung.yaml | 70 +++++++++++++++++++ 2 files changed, 70 insertions(+), 45 deletions(-) delete mode 100644 Documentation/devicetree/bindings/power/pd-samsung.txt create mode 100644 Documentation/devicetree/bindings/power/pd-samsung.yaml
Documentation/devicetree/bindings/power/pd-samsung.txt deleted +0 -45
@@ -1,45 +0,0 @@ -* Samsung Exynos Power Domains - -Exynos processors include support for multiple power domains which are used -to gate power to one or more peripherals on the processor. - -Required Properties: -- compatible: should be one of the following. - * samsung,exynos4210-pd - for exynos4210 type power domain. - * samsung,exynos5433-pd - for exynos5433 type power domain. -- reg: physical base address of the controller and length of memory mapped - region. -- #power-domain-cells: number of cells in power domain specifier; - must be 0. - -Optional Properties: -- label: Human readable string with domain name. Will be visible in userspace - to let user to distinguish between multiple domains in SoC. -- power-domains: phandle pointing to the parent power domain, for more details - see Documentation/devicetree/bindings/power/power_domain.txt - -Deprecated Properties: -- clocks -- clock-names - -Node of a device using power domains must have a power-domains property -defined with a phandle to respective power domain. - -Example: - - lcd0: power-domain-lcd0 { - compatible = "samsung,exynos4210-pd"; - reg = <0x10023C00 0x10>; - #power-domain-cells = <0>; - label = "LCD0"; - }; - - mfc_pd: power-domain@10044060 { - compatible = "samsung,exynos4210-pd"; - reg = <0x10044060 0x20>; - #power-domain-cells = <0>; - label = "MFC"; - }; - -See Documentation/devicetree/bindings/power/power_domain.txt for description -of consumer-side bindings.
Documentation/devicetree/bindings/power/pd-samsung.yaml new file +70 -0
70 lines not on this page · raw message
Signature · 1 line
2.17.1
Rob Herring
maintainerRe: [RFC 2/2] dt-bindings: power: Convert Samsung Exynos Power Domain bindings to json-schema
Quoted 95 lines · Krzysztof Kozlowski
Convert Samsung Exynos Soc Power Domain bindings to DT schema format using json-schema.
Signed-off-by Krzysztof Kozlowski <[email protected]>--- .../devicetree/bindings/power/pd-samsung.txt | 45 ------------ .../devicetree/bindings/power/pd-samsung.yaml | 70 +++++++++++++++++++ 2 files changed, 70 insertions(+), 45 deletions(-) delete mode 100644 Documentation/devicetree/bindings/power/pd-samsung.txt create mode 100644 Documentation/devicetree/bindings/power/pd-samsung.yamlDocumentation/devicetree/bindings/power/pd-samsung.txt deleted +0
-45@@ -1,45 +0,0 @@ -* Samsung Exynos Power Domains - -Exynos processors include support for multiple power domains which are used -to gate power to one or more peripherals on the processor. - -Required Properties: -- compatible: should be one of the following. - * samsung,exynos4210-pd - for exynos4210 type power domain. - * samsung,exynos5433-pd - for exynos5433 type power domain. -- reg: physical base address of the controller and length of memory mapped - region. -- #power-domain-cells: number of cells in power domain specifier; - must be 0. - -Optional Properties: -- label: Human readable string with domain name. Will be visible in userspace - to let user to distinguish between multiple domains in SoC. -- power-domains: phandle pointing to the parent power domain, for more details - see Documentation/devicetree/bindings/power/power_domain.txt - -Deprecated Properties: -- clocks -- clock-names - -Node of a device using power domains must have a power-domains property -defined with a phandle to respective power domain. - -Example: - - lcd0: power-domain-lcd0 { - compatible = "samsung,exynos4210-pd"; - reg = <0x10023C00 0x10>; - #power-domain-cells = <0>; - label = "LCD0"; - }; - - mfc_pd: power-domain@10044060 { - compatible = "samsung,exynos4210-pd"; - reg = <0x10044060 0x20>; - #power-domain-cells = <0>; - label = "MFC"; - }; - -See Documentation/devicetree/bindings/power/power_domain.txt for description -of consumer-side bindings.Documentation/devicetree/bindings/power/pd-samsung.yaml new file +27
-0@@ -0,0 +1,70 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/power/pd-samsung.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Samsung Exynos SoC Power Domains + +maintainers: + - Krzysztof Kozlowski <[email protected]> + +description: |+ + Exynos processors include support for multiple power domains which are used + to gate power to one or more peripherals on the processor. + +allOf: + - $ref: power-domain.yaml# + +properties: + compatible: + enum: + - samsung,exynos4210-pd + - samsung,exynos5433-pd + + reg: + maxItems: 1 +
Documentation/devicetree/bindings/power/pd-samsung.yaml line 37
Quoted 10 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml new file +10
-0+ clocks: + deprecated: true + maxItems: 1 + + clock-names: + deprecated: true + maxItems: 1 + + label: + $ref: /schemas/types.yaml#/definitions/string
label already has a type.
Is there a defined set of values?
Documentation/devicetree/bindings/power/pd-samsung.yaml line 46
Quoted 9 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml new file +9
-0+ description: + Human readable string with domain name. Will be visible in userspace + to let user to distinguish between multiple domains in SoC. + + "#power-domain-cells": + const: 0 + + power-domains: + $ref: /schemas/types.yaml#/definitions/phandle
Already has a type.
maxItems: 1
Documentation/devicetree/bindings/power/pd-samsung.yaml line 49
Quoted 3 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml new file +3
-0+ description: + Phandle pointing to the parent power domain, for more details + see power-domain-consumers.yaml.
Unless there's something specific about this device to say, drop this.
Quoted 24 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml new file +21
-0+ +required: + - compatible + - "#power-domain-cells" + - reg + +examples: + - | + lcd0: power-domain-lcd0 { + compatible = "samsung,exynos4210-pd"; + reg = <0x10023C00 0x10>; + #power-domain-cells = <0>; + label = "LCD0"; + }; + + mfc_pd: power-domain@10044060 { + compatible = "samsung,exynos4210-pd"; + reg = <0x10044060 0x20>; + #power-domain-cells = <0>; + label = "MFC"; + };Signature · 1 line
2.17.1
Krzysztof Kozlowski
maintainerRe: [RFC 2/2] dt-bindings: power: Convert Samsung Exynos Power Domain bindings to json-schema
Quoted 109 lines · Rob Herring
Quoted 95 lines · Krzysztof Kozlowski
Convert Samsung Exynos Soc Power Domain bindings to DT schema format using json-schema.
Signed-off-by Krzysztof Kozlowski <[email protected]>--- .../devicetree/bindings/power/pd-samsung.txt | 45 ------------ .../devicetree/bindings/power/pd-samsung.yaml | 70 +++++++++++++++++++ 2 files changed, 70 insertions(+), 45 deletions(-) delete mode 100644 Documentation/devicetree/bindings/power/pd-samsung.txt create mode 100644 Documentation/devicetree/bindings/power/pd-samsung.yamlDocumentation/devicetree/bindings/power/pd-samsung.txt deleted +0
-45@@ -1,45 +0,0 @@ -* Samsung Exynos Power Domains - -Exynos processors include support for multiple power domains which are used -to gate power to one or more peripherals on the processor. - -Required Properties: -- compatible: should be one of the following. - * samsung,exynos4210-pd - for exynos4210 type power domain. - * samsung,exynos5433-pd - for exynos5433 type power domain. -- reg: physical base address of the controller and length of memory mapped - region. -- #power-domain-cells: number of cells in power domain specifier; - must be 0. - -Optional Properties: -- label: Human readable string with domain name. Will be visible in userspace - to let user to distinguish between multiple domains in SoC. -- power-domains: phandle pointing to the parent power domain, for more details - see Documentation/devicetree/bindings/power/power_domain.txt - -Deprecated Properties: -- clocks -- clock-names - -Node of a device using power domains must have a power-domains property -defined with a phandle to respective power domain. - -Example: - - lcd0: power-domain-lcd0 { - compatible = "samsung,exynos4210-pd"; - reg = <0x10023C00 0x10>; - #power-domain-cells = <0>; - label = "LCD0"; - }; - - mfc_pd: power-domain@10044060 { - compatible = "samsung,exynos4210-pd"; - reg = <0x10044060 0x20>; - #power-domain-cells = <0>; - label = "MFC"; - }; - -See Documentation/devicetree/bindings/power/power_domain.txt for description -of consumer-side bindings.Documentation/devicetree/bindings/power/pd-samsung.yaml new file +27
-0@@ -0,0 +1,70 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/power/pd-samsung.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Samsung Exynos SoC Power Domains + +maintainers: + - Krzysztof Kozlowski <[email protected]> + +description: |+ + Exynos processors include support for multiple power domains which are used + to gate power to one or more peripherals on the processor. + +allOf: + - $ref: power-domain.yaml# + +properties: + compatible: + enum: + - samsung,exynos4210-pd + - samsung,exynos5433-pd + + reg: + maxItems: 1 +Documentation/devicetree/bindings/power/pd-samsung.yaml line 37
Quoted 10 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml new file +10
-0+ clocks: + deprecated: true + maxItems: 1 + + clock-names: + deprecated: true + maxItems: 1 + + label: + $ref: /schemas/types.yaml#/definitions/stringlabel already has a type.
Quoted 1 line
Is there a defined set of values?
No, many Exynos SoCs have similar values but newer designs are bringing new names.
Quoted 13 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml line 46
Quoted 10 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml new file +9
-0+ description: + Human readable string with domain name. Will be visible in userspace + to let user to distinguish between multiple domains in SoC. + + "#power-domain-cells": + const: 0 + + power-domains: + $ref: /schemas/types.yaml#/definitions/phandleAlready has a type.
Quoted 1 line
maxItems: 1
OK
Quoted 6 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml line 49
Quoted 4 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml new file +3
-0+ description: + Phandle pointing to the parent power domain, for more details + see power-domain-consumers.yaml.Unless there's something specific about this device to say, drop this.
Sure.
Best regards,
Krzysztof
Quoted 25 lines
Quoted 25 lines
Documentation/devicetree/bindings/power/pd-samsung.yaml new file +21
-0+ +required: + - compatible + - "#power-domain-cells" + - reg + +examples: + - | + lcd0: power-domain-lcd0 { + compatible = "samsung,exynos4210-pd"; + reg = <0x10023C00 0x10>; + #power-domain-cells = <0>; + label = "LCD0"; + }; + + mfc_pd: power-domain@10044060 { + compatible = "samsung,exynos4210-pd"; + reg = <0x10044060 0x20>; + #power-domain-cells = <0>; + label = "MFC"; + };Signature · 1 line
2.17.1
Rob Herring
maintainerQuoted 9 lines · Krzysztof Kozlowski
Convert Generic Power Domain bindings to DT schema format using json-schema. The consumer bindings are split to separate file.
Signed-off-by Krzysztof Kozlowski <[email protected]>---
TODO:
1. How the consumer bindings should match nodes?
How it already done. The consumer binding is always applied so we always apply the type schema to the consumer properties. Device specific bindings have to list the consumer properties because they need to define how many power domains and the names.
Quoted 3 lines
2. Somehow the example complains:
Documentation/devicetree/bindings/power/power-domain.example.dt.yaml: power-controller@12341000: power-domains:0: [1, 0] is too longDocumentation/devicetree/bindings/power/power-domain.example.dt.yaml: power-controller@12341000: power-domains:0:1: missing phandle tag in 0
You used 'phandle' instead of 'phandle-array'. If you have cells, the latter is used. Perhaps we should distinguish between having cells or no cells.
Quoted 3 lines
3. Current matching by node name causes false positives:
arch/arm/boot/dts/am335x-icev2.dt.yaml: power-controller@2d: '#power-domain-cells' is a required propertyarch/arm/boot/dts/qcom-apq8064-cm-qs600.dt.yaml: power-controller@2099000: '#power-domain-cells' is a required property
They should have different node names if they are not power-domain providers.
Quoted 74 lines
--- .../devicetree/bindings/arm/arm,scmi.txt | 2 +- .../devicetree/bindings/arm/arm,scpi.txt | 2 +- .../bindings/arm/freescale/fsl,scu.txt | 2 +- .../bindings/clock/clk-exynos-audss.txt | 2 +- .../bindings/clock/exynos5433-clock.txt | 4 +- .../bindings/clock/renesas,cpg-mssr.txt | 2 +- .../clock/renesas,r8a7778-cpg-clocks.txt | 2 +- .../clock/renesas,r8a7779-cpg-clocks.txt | 2 +- .../clock/renesas,rcar-gen2-cpg-clocks.txt | 2 +- .../bindings/clock/renesas,rz-cpg-clocks.txt | 2 +- .../bindings/clock/ti/davinci/psc.txt | 2 +- .../bindings/display/etnaviv/etnaviv-drm.txt | 2 +- .../devicetree/bindings/display/msm/dpu.txt | 2 +- .../devicetree/bindings/display/msm/mdp5.txt | 2 +- .../devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- .../firmware/nvidia,tegra186-bpmp.txt | 2 +- .../bindings/media/imx7-mipi-csi2.txt | 3 +- .../bindings/media/mediatek-jpeg-decoder.txt | 3 +- .../bindings/media/mediatek-mdp.txt | 3 +- .../bindings/opp/qcom-nvmem-cpufreq.txt | 2 +- .../devicetree/bindings/pci/pci-keystone.txt | 2 +- .../bindings/phy/ti,phy-am654-serdes.txt | 2 +- .../bindings/power/amlogic,meson-gx-pwrc.txt | 2 +- .../devicetree/bindings/power/fsl,imx-gpc.txt | 2 +- .../bindings/power/fsl,imx-gpcv2.txt | 2 +- .../power/power-domain-consumers.yaml | 124 +++++++++++ .../bindings/power/power-domain.yaml | 136 ++++++++++++ .../bindings/power/power_domain.txt | 205 ------------------ .../devicetree/bindings/power/qcom,rpmpd.txt | 2 +- .../bindings/power/renesas,rcar-sysc.txt | 2 +- .../bindings/power/renesas,sysc-rmobile.txt | 2 +- .../bindings/power/xlnx,zynqmp-genpd.txt | 2 +- .../bindings/soc/bcm/brcm,bcm2835-pm.txt | 2 +- .../bindings/soc/mediatek/scpsys.txt | 2 +- .../bindings/soc/ti/sci-pm-domain.txt | 2 +- .../bindings/usb/nvidia,tegra124-xusb.txt | 4 +- MAINTAINERS | 2 +- 37 files changed, 299 insertions(+), 241 deletions(-) create mode 100644 Documentation/devicetree/bindings/power/power-domain-consumers.yaml create mode 100644 Documentation/devicetree/bindings/power/power-domain.yaml delete mode 100644 Documentation/devicetree/bindings/power/power_domain.txtDocumentation/devicetree/bindings/power/power-domain-consumers.yaml new file +24
-0@@ -0,0 +1,124 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/power/power-domain-consumers.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: PM domain consumers + +maintainers: + - Rafael J. Wysocki <[email protected]> + - Kevin Hilman <[email protected]> + - Ulf Hansson <[email protected]> + +description: |+ + See power-domain.yaml + +allOf: + - $ref: /schemas/power-domain/power-domain-consumer.yaml + +# TODO: missing select (compatible?) + +properties: + power-domains: + $ref: /schemas/types.yaml#/definitions/phandle-array
Documentation/devicetree/bindings/power/power-domain-consumers.yaml line 34
Quoted 10 lines
Documentation/devicetree/bindings/power/power-domain-consumers.yaml new file +10
-0+ description: + A list of PM domain specifiers, as defined by bindings of the power + controller that is the PM domain provider. + + power-domain-names: + $ref: /schemas/types.yaml#/definitions/string-array + description: + A list of power domain name strings sorted in the same order + as the power-domains property. Consumers drivers will use + power-domain-names to match power domains with power-domains specifiers.
Why are we duplicating this?
Quoted 132 lines
Documentation/devicetree/bindings/power/power-domain-consumers.yaml new file +90
-0+ + required-opps: + $ref: /schemas/types.yaml#/definitions/phandle + description: + This contains phandle to an OPP node in another device's OPP table. + It may contain an array of phandles, where each phandle points to an OPP + of a different device. It should not contain multiple phandles to the OPP + nodes in the same OPP table. This specifies the minimum required OPP + of the device(s), whose OPP's phandle is present in this property, + for the functioning of the current device at the current OPP (where this + property is present). + +required: + - power-domains + +dependencies: + power-domain-names: [ power-domains ] + +examples: + - | + leaky-device@12350000 { + compatible = "foo,i-leak-current"; + reg = <0x12350000 0x1000>; + power-domains = <&power 0>; + power-domain-names = "io"; + }; + + leaky-device@12351000 { + compatible = "foo,i-leak-current"; + reg = <0x12351000 0x1000>; + power-domains = <&power 0>, <&power 1> ; + power-domain-names = "io", "clk"; + }; + + // The first example above defines a typical PM domain consumer device, which is + // located inside a PM domain with index 0 of a power controller represented by a + // node with the label "power". + // In the second example the consumer device are partitioned across two PM domains, + // the first with index 0 and the second with index 1, of a power controller that + // is represented by a node with the label "power". + + - | + // Example with OPP table for domain provider that provides two domains: + + domain0_opp_table: opp-table0 { + compatible = "operating-points-v2"; + + domain0_opp_0: opp-1000000000 { + opp-hz = /bits/ 64 <1000000000>; + opp-microvolt = <975000 970000 985000>; + }; + domain0_opp_1: opp-1100000000 { + opp-hz = /bits/ 64 <1100000000>; + opp-microvolt = <1000000 980000 1010000>; + }; + }; + + domain1_opp_table: opp-table1 { + compatible = "operating-points-v2"; + + domain1_opp_0: opp-1200000000 { + opp-hz = /bits/ 64 <1200000000>; + opp-microvolt = <975000 970000 985000>; + }; + domain1_opp_1: opp-1300000000 { + opp-hz = /bits/ 64 <1300000000>; + opp-microvolt = <1000000 980000 1010000>; + }; + }; + + power: power-controller@12340000 { + compatible = "foo,power-controller"; + reg = <0x12340000 0x1000>; + #power-domain-cells = <1>; + operating-points-v2 = <&domain0_opp_table>, <&domain1_opp_table>; + }; + + leaky-device0@12350000 { + compatible = "foo,i-leak-current"; + reg = <0x12350000 0x1000>; + power-domains = <&power 0>; + required-opps = <&domain0_opp_0>; + }; + + leaky-device1@12350000 { + compatible = "foo,i-leak-current"; + reg = <0x12350000 0x1000>; + power-domains = <&power 1>; + required-opps = <&domain1_opp_1>; + };Documentation/devicetree/bindings/power/power-domain.yaml new file +36
-0@@ -0,0 +1,136 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/power/power-domain.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Generic PM domains + +maintainers: + - Rafael J. Wysocki <[email protected]> + - Kevin Hilman <[email protected]> + - Ulf Hansson <[email protected]> + +description: |+ + System on chip designs are often divided into multiple PM domains that can be + used for power gating of selected IP blocks for power saving by reduced leakage + current. + + This device tree binding can be used to bind PM domain consumer devices with + their PM domains provided by PM domain providers. A PM domain provider can be + represented by any node in the device tree and can provide one or more PM + domains. A consumer node can refer to the provider by a phandle and a set of + phandle arguments (so called PM domain specifiers) of length specified by the + \#power-domain-cells property in the PM domain provider node. + +properties: + $nodename: + pattern: "^(power-controller|power-domain)(@.*)?" + + domain-idle-states: + $ref: /schemas/types.yaml#/definitions/phandle-array + description: + A phandle of an idle-state that shall be soaked into a generic domain + power state. The idle state definitions are compatible with + domain-idle-state specified in + Documentation/devicetree/bindings/power/domain-idle-state.txt
Documentation/devicetree/bindings/power/power-domain.yaml line 46
Quoted 10 lines
Documentation/devicetree/bindings/power/power-domain.yaml new file +10
-0+ phandles that are not compatible with domain-idle-state will be ignored. + The domain-idle-state property reflects the idle state of this PM domain + and not the idle states of the devices or sub-domains in the PM domain. + Devices and sub-domains have their own idle-states independent + of the parent domain's idle states. In the absence of this property, + the domain would be considered as capable of being powered-on + or powered-off. + + operating-points-v2: + $ref: /schemas/types.yaml#/definitions/phandle-array
This needs to be defined as part of an OPP schema. I guess there's some value listing it here, but a device specific binding will still have to list it to define how many entries.
Documentation/devicetree/bindings/power/power-domain.yaml line 55
Quoted 9 lines
Documentation/devicetree/bindings/power/power-domain.yaml new file +9
-0+ description: + Phandles to the OPP tables of power domains provided by a power domain + provider. If the provider provides a single power domain only or all + the power domains provided by the provider have identical OPP tables, + then this shall contain a single phandle. Refer to ../opp/opp.txt + for more information. + + "#power-domain-cells": + $ref: /schemas/types.yaml#/definitions/uint32
Strictly speaking, we don't need to define the type as '#.*-cells' has a type.
Documentation/devicetree/bindings/power/power-domain.yaml line 63
Quoted 8 lines
Documentation/devicetree/bindings/power/power-domain.yaml new file +8
-0+ description: + Number of cells in a PM domain specifier. Typically 0 for nodes + representing a single PM domain and 1 for nodes providing multiple PM + domains (e.g. power controllers), but can be any value as specified + by device tree binding documentation of particular provider. + + power-domains: + $ref: /schemas/types.yaml#/definitions/phandle
Don't need type here either.
Quoted 73 lines
Documentation/devicetree/bindings/power/power-domain.yaml new file +73
-0+ description: + A phandle and PM domain specifier as defined by bindings of the power + controller specified by phandle. Some power domains might be powered + from another power domain (or have other hardware specific + dependencies). For representing such dependency a standard PM domain + consumer binding is used. When provided, all domains created + by the given provider should be subdomains of the domain specified + by this binding. More details about power domain specifier are + available in the power-domain-consumers.yaml. + +required: + - "#power-domain-cells" + +examples: + - | + power: power-controller@12340000 { + compatible = "foo,power-controller"; + reg = <0x12340000 0x1000>; + #power-domain-cells = <1>; + }; + + // The node above defines a power controller that is a PM domain provider and + // expects one cell as its phandle argument. + + - | + parent2: power-controller@12340000 { + compatible = "foo,power-controller"; + reg = <0x12340000 0x1000>; + #power-domain-cells = <1>; + }; + + child2: power-controller@12341000 { + compatible = "foo,power-controller"; + reg = <0x12341000 0x1000>; + power-domains = <&parent2 0>; + #power-domain-cells = <1>; + }; + + // The nodes above define two power controllers: 'parent' and 'child'. + // Domains created by the 'child' power controller are subdomains of '0' power + // domain provided by the 'parent' power controller. + + - | + parent3: power-controller@12340000 { + compatible = "foo,power-controller"; + reg = <0x12340000 0x1000>; + #power-domain-cells = <0>; + domain-idle-states = <&DOMAIN_RET>, <&DOMAIN_PWR_DN>; + }; + + child3: power-controller@12341000 { + compatible = "foo,power-controller"; + reg = <0x12341000 0x1000>; + power-domains = <&parent3>; + #power-domain-cells = <0>; + domain-idle-states = <&DOMAIN_PWR_DN>; + }; + + DOMAIN_RET: state@0 { + compatible = "domain-idle-state"; + reg = <0x0 0x0>; + entry-latency-us = <1000>; + exit-latency-us = <2000>; + min-residency-us = <10000>; + }; + + DOMAIN_PWR_DN: state@1 { + compatible = "domain-idle-state"; + reg = <0x1 0x0>; + entry-latency-us = <5000>; + exit-latency-us = <8000>; + min-residency-us = <7000>; + };
Krzysztof Kozlowski
maintainerQuoted 8 lines · Rob Herring
Quoted 7 lines · Krzysztof Kozlowski
Convert Generic Power Domain bindings to DT schema format using json-schema. The consumer bindings are split to separate file.
Signed-off-by Krzysztof Kozlowski <[email protected]>---
Quoted 7 lines
Quoted 2 lines
TODO:
1. How the consumer bindings should match nodes?How it already done. The consumer binding is always applied so we always apply the type schema to the consumer properties. Device specific bindings have to list the consumer properties because they need to define how many power domains and the names.
I'll apply then select:true so the "required-opps" will be matched.
Quoted 8 lines
Quoted 4 lines
2. Somehow the example complains:
Documentation/devicetree/bindings/power/power-domain.example.dt.yaml: power-controller@12341000: power-domains:0: [1, 0] is too longDocumentation/devicetree/bindings/power/power-domain.example.dt.yaml: power-controller@12341000: power-domains:0:1: missing phandle tag in 0You used 'phandle' instead of 'phandle-array'. If you have cells, the latter is used. Perhaps we should distinguish between having cells or no cells.
Thanks, I'll drop it anyway as it is duplicating dt-schema.
Quoted 86 lines
Quoted 4 lines
3. Current matching by node name causes false positives:
arch/arm/boot/dts/am335x-icev2.dt.yaml: power-controller@2d: '#power-domain-cells' is a required propertyarch/arm/boot/dts/qcom-apq8064-cm-qs600.dt.yaml: power-controller@2099000: '#power-domain-cells' is a required propertyThey should have different node names if they are not power-domain providers.
Quoted 78 lines
--- .../devicetree/bindings/arm/arm,scmi.txt | 2 +- .../devicetree/bindings/arm/arm,scpi.txt | 2 +- .../bindings/arm/freescale/fsl,scu.txt | 2 +- .../bindings/clock/clk-exynos-audss.txt | 2 +- .../bindings/clock/exynos5433-clock.txt | 4 +- .../bindings/clock/renesas,cpg-mssr.txt | 2 +- .../clock/renesas,r8a7778-cpg-clocks.txt | 2 +- .../clock/renesas,r8a7779-cpg-clocks.txt | 2 +- .../clock/renesas,rcar-gen2-cpg-clocks.txt | 2 +- .../bindings/clock/renesas,rz-cpg-clocks.txt | 2 +- .../bindings/clock/ti/davinci/psc.txt | 2 +- .../bindings/display/etnaviv/etnaviv-drm.txt | 2 +- .../devicetree/bindings/display/msm/dpu.txt | 2 +- .../devicetree/bindings/display/msm/mdp5.txt | 2 +- .../devicetree/bindings/dsp/fsl,dsp.yaml | 2 +- .../firmware/nvidia,tegra186-bpmp.txt | 2 +- .../bindings/media/imx7-mipi-csi2.txt | 3 +- .../bindings/media/mediatek-jpeg-decoder.txt | 3 +- .../bindings/media/mediatek-mdp.txt | 3 +- .../bindings/opp/qcom-nvmem-cpufreq.txt | 2 +- .../devicetree/bindings/pci/pci-keystone.txt | 2 +- .../bindings/phy/ti,phy-am654-serdes.txt | 2 +- .../bindings/power/amlogic,meson-gx-pwrc.txt | 2 +- .../devicetree/bindings/power/fsl,imx-gpc.txt | 2 +- .../bindings/power/fsl,imx-gpcv2.txt | 2 +- .../power/power-domain-consumers.yaml | 124 +++++++++++ .../bindings/power/power-domain.yaml | 136 ++++++++++++ .../bindings/power/power_domain.txt | 205 ------------------ .../devicetree/bindings/power/qcom,rpmpd.txt | 2 +- .../bindings/power/renesas,rcar-sysc.txt | 2 +- .../bindings/power/renesas,sysc-rmobile.txt | 2 +- .../bindings/power/xlnx,zynqmp-genpd.txt | 2 +- .../bindings/soc/bcm/brcm,bcm2835-pm.txt | 2 +- .../bindings/soc/mediatek/scpsys.txt | 2 +- .../bindings/soc/ti/sci-pm-domain.txt | 2 +- .../bindings/usb/nvidia,tegra124-xusb.txt | 4 +- MAINTAINERS | 2 +- 37 files changed, 299 insertions(+), 241 deletions(-) create mode 100644 Documentation/devicetree/bindings/power/power-domain-consumers.yaml create mode 100644 Documentation/devicetree/bindings/power/power-domain.yaml delete mode 100644 Documentation/devicetree/bindings/power/power_domain.txtDocumentation/devicetree/bindings/power/power-domain-consumers.yaml new file +28
-0@@ -0,0 +1,124 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/power/power-domain-consumers.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: PM domain consumers + +maintainers: + - Rafael J. Wysocki <[email protected]> + - Kevin Hilman <[email protected]> + - Ulf Hansson <[email protected]> + +description: |+ + See power-domain.yaml + +allOf: + - $ref: /schemas/power-domain/power-domain-consumer.yaml + +# TODO: missing select (compatible?) + +properties: + power-domains: + $ref: /schemas/types.yaml#/definitions/phandle-array + description: + A list of PM domain specifiers, as defined by bindings of the power + controller that is the PM domain provider. +
Quoted 8 lines
Documentation/devicetree/bindings/power/power-domain-consumers.yaml line 34
Quoted 6 lines
Documentation/devicetree/bindings/power/power-domain-consumers.yaml new file +6
-0+ power-domain-names: + $ref: /schemas/types.yaml#/definitions/string-array + description: + A list of power domain name strings sorted in the same order + as the power-domains property. Consumers drivers will use + power-domain-names to match power domains with power-domains specifiers.Why are we duplicating this?
My bad.
Quoted 139 lines
Quoted 139 lines
Documentation/devicetree/bindings/power/power-domain-consumers.yaml new file +90
-0+ + required-opps: + $ref: /schemas/types.yaml#/definitions/phandle + description: + This contains phandle to an OPP node in another device's OPP table. + It may contain an array of phandles, where each phandle points to an OPP + of a different device. It should not contain multiple phandles to the OPP + nodes in the same OPP table. This specifies the minimum required OPP + of the device(s), whose OPP's phandle is present in this property, + for the functioning of the current device at the current OPP (where this + property is present). + +required: + - power-domains + +dependencies: + power-domain-names: [ power-domains ] + +examples: + - | + leaky-device@12350000 { + compatible = "foo,i-leak-current"; + reg = <0x12350000 0x1000>; + power-domains = <&power 0>; + power-domain-names = "io"; + }; + + leaky-device@12351000 { + compatible = "foo,i-leak-current"; + reg = <0x12351000 0x1000>; + power-domains = <&power 0>, <&power 1> ; + power-domain-names = "io", "clk"; + }; + + // The first example above defines a typical PM domain consumer device, which is + // located inside a PM domain with index 0 of a power controller represented by a + // node with the label "power". + // In the second example the consumer device are partitioned across two PM domains, + // the first with index 0 and the second with index 1, of a power controller that + // is represented by a node with the label "power". + + - | + // Example with OPP table for domain provider that provides two domains: + + domain0_opp_table: opp-table0 { + compatible = "operating-points-v2"; + + domain0_opp_0: opp-1000000000 { + opp-hz = /bits/ 64 <1000000000>; + opp-microvolt = <975000 970000 985000>; + }; + domain0_opp_1: opp-1100000000 { + opp-hz = /bits/ 64 <1100000000>; + opp-microvolt = <1000000 980000 1010000>; + }; + }; + + domain1_opp_table: opp-table1 { + compatible = "operating-points-v2"; + + domain1_opp_0: opp-1200000000 { + opp-hz = /bits/ 64 <1200000000>; + opp-microvolt = <975000 970000 985000>; + }; + domain1_opp_1: opp-1300000000 { + opp-hz = /bits/ 64 <1300000000>; + opp-microvolt = <1000000 980000 1010000>; + }; + }; + + power: power-controller@12340000 { + compatible = "foo,power-controller"; + reg = <0x12340000 0x1000>; + #power-domain-cells = <1>; + operating-points-v2 = <&domain0_opp_table>, <&domain1_opp_table>; + }; + + leaky-device0@12350000 { + compatible = "foo,i-leak-current"; + reg = <0x12350000 0x1000>; + power-domains = <&power 0>; + required-opps = <&domain0_opp_0>; + }; + + leaky-device1@12350000 { + compatible = "foo,i-leak-current"; + reg = <0x12350000 0x1000>; + power-domains = <&power 1>; + required-opps = <&domain1_opp_1>; + };Documentation/devicetree/bindings/power/power-domain.yaml new file +42
-0@@ -0,0 +1,136 @@ +# SPDX-License-Identifier: GPL-2.0 +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/power/power-domain.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Generic PM domains + +maintainers: + - Rafael J. Wysocki <[email protected]> + - Kevin Hilman <[email protected]> + - Ulf Hansson <[email protected]> + +description: |+ + System on chip designs are often divided into multiple PM domains that can be + used for power gating of selected IP blocks for power saving by reduced leakage + current. + + This device tree binding can be used to bind PM domain consumer devices with + their PM domains provided by PM domain providers. A PM domain provider can be + represented by any node in the device tree and can provide one or more PM + domains. A consumer node can refer to the provider by a phandle and a set of + phandle arguments (so called PM domain specifiers) of length specified by the + \#power-domain-cells property in the PM domain provider node. + +properties: + $nodename: + pattern: "^(power-controller|power-domain)(@.*)?" + + domain-idle-states: + $ref: /schemas/types.yaml#/definitions/phandle-array + description: + A phandle of an idle-state that shall be soaked into a generic domain + power state. The idle state definitions are compatible with + domain-idle-state specified in + Documentation/devicetree/bindings/power/domain-idle-state.txt + phandles that are not compatible with domain-idle-state will be ignored. + The domain-idle-state property reflects the idle state of this PM domain + and not the idle states of the devices or sub-domains in the PM domain. + Devices and sub-domains have their own idle-states independent + of the parent domain's idle states. In the absence of this property, + the domain would be considered as capable of being powered-on
Quoted 8 lines
Documentation/devicetree/bindings/power/power-domain.yaml line 46
Quoted 4 lines
Documentation/devicetree/bindings/power/power-domain.yaml new file +4
-0+ or powered-off. + + operating-points-v2: + $ref: /schemas/types.yaml#/definitions/phandle-arrayThis needs to be defined as part of an OPP schema. I guess there's some value listing it here, but a device specific binding will still have to list it to define how many entries.
So for now I'll leave it here. Consecutive patches can split it.
Quoted 11 lines
Documentation/devicetree/bindings/power/power-domain.yaml line 55
Quoted 10 lines
Documentation/devicetree/bindings/power/power-domain.yaml new file +9
-0+ description: + Phandles to the OPP tables of power domains provided by a power domain + provider. If the provider provides a single power domain only or all + the power domains provided by the provider have identical OPP tables, + then this shall contain a single phandle. Refer to ../opp/opp.txt + for more information. + + "#power-domain-cells": + $ref: /schemas/types.yaml#/definitions/uint32
Quoted 2 lines
Strictly speaking, we don't need to define the type as '#.*-cells' has a type.
OK
Quoted 11 lines
Documentation/devicetree/bindings/power/power-domain.yaml line 63
Quoted 9 lines
Documentation/devicetree/bindings/power/power-domain.yaml new file +8
-0+ description: + Number of cells in a PM domain specifier. Typically 0 for nodes + representing a single PM domain and 1 for nodes providing multiple PM + domains (e.g. power controllers), but can be any value as specified + by device tree binding documentation of particular provider. + + power-domains: + $ref: /schemas/types.yaml#/definitions/phandleDon't need type here either.
OK
Best regards,
Krzysztof