[PATCH 1/3] dt-bindings: add multidomain support to i.MX GPC DT binding
p.zabel at pengutronix.de
Mon Nov 23 07:31:32 PST 2015
Am Montag, den 23.11.2015, 16:07 +0100 schrieb Lucas Stach:
> This adds a new binding for the Freescale i.MX GPC block, which allows
> to describe multiple power domains in a more natural way. The driver
> will continue to support the old binding for existing DTBs, but new
> features like the additional domains present on i.MX6SX will only be
> usable with the new binding.
> Signed-off-by: Lucas Stach <l.stach at pengutronix.de>
> .../devicetree/bindings/power/fsl,imx-gpc.txt | 81 ++++++++++++++--------
> 1 file changed, 54 insertions(+), 27 deletions(-)
> diff --git a/Documentation/devicetree/bindings/power/fsl,imx-gpc.txt b/Documentation/devicetree/bindings/power/fsl,imx-gpc.txt
> index 65cc0345747d..0b777b623812 100644
> --- a/Documentation/devicetree/bindings/power/fsl,imx-gpc.txt
> +++ b/Documentation/devicetree/bindings/power/fsl,imx-gpc.txt
> @@ -1,22 +1,41 @@
> Freescale i.MX General Power Controller
> -The i.MX6Q General Power Control (GPC) block contains DVFS load tracking
> -counters and Power Gating Control (PGC) for the CPU and PU (GPU/VPU) power
> +The i.MX6 General Power Control (GPC) block contains DVFS load tracking
> +counters and Power Gating Control (PGC).
> Required properties:
> - compatible: Should be "fsl,imx6q-gpc" or "fsl,imx6sl-gpc"
> - reg: should be register base and length as documented in the
> -- interrupts: Should contain GPC interrupt request 1
> -- pu-supply: Link to the LDO regulator powering the PU power domain
> -- clocks: Clock phandles to devices in the PU power domain that need
> - to be enabled during domain power-up for reset propagation.
> -- #power-domain-cells: Should be 1, see below:
> +- interrupts: Should contain GPC interrupts
> +- clocks: Must contain an entry for each entry in clock-names.
> + See Documentation/devicetree/bindings/clocks/clock-bindings.txt for details.
> +- clock-names: Must include the following entries:
> + - ipg
As long as there is just a single clock input, shouldn't we just remove
the clock-names property?
Acked-by: Philipp Zabel <p.zabel at pengutronix.de>
More information about the linux-arm-kernel