From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] dt-bindings: power: Add ZynqMP power domain bindings
Date: Mon, 5 Mar 2018 16:39:05 -0600 [thread overview]
Message-ID: <20180305223905.65nnunv63fyg7bye@rob-hp-laptop> (raw)
In-Reply-To: <1519775750-21297-2-git-send-email-jollys@xilinx.com>
On Tue, Feb 27, 2018 at 03:55:49PM -0800, Jolly Shah wrote:
> Add documentation to describe ZynqMP power domain bindings.
>
> Signed-off-by: Jolly Shah <jollys@xilinx.com>
> Signed-off-by: Rajan Vaja <rajanv@xilinx.com>
> ---
> .../devicetree/bindings/power/zynqmp-genpd.txt | 46 ++++++++++++++++++++++
> 1 file changed, 46 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/power/zynqmp-genpd.txt
>
> diff --git a/Documentation/devicetree/bindings/power/zynqmp-genpd.txt b/Documentation/devicetree/bindings/power/zynqmp-genpd.txt
> new file mode 100644
> index 0000000..25f9711
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/power/zynqmp-genpd.txt
> @@ -0,0 +1,46 @@
> +Device Tree bindings for Xilinx Zynq MPSoC PM domains
> +
> +The binding for zynqmp-genpd follow the common generic PM domain binding[1].
> +
> +[1] Documentation/devicetree/bindings/power/power_domain.txt
> +
> +== Zynq MPSoC Generic PM Domain Node ==
> +
> +Required properties:
> + - compatible: Must be: "xlnx,zynqmp-genpd"
genpd is a Linux term. The DT should contain a power controller that
controls physical power islands on a chip.
> +
> +This node contains a number of subnodes, each representing a single PM domain
> +that PM domain consumer devices reference.
> +
> +== PM Domain Nodes ==
> +
> +Required properties:
> + - #power-domain-cells: Number of cells in a PM domain specifier. Must be 0.
> + - pd-id: List of domain identifiers of as defined by platform firmware. These
> + identifiers are passed to the PM firmware.
> +
> +Example:
> + zynqmp-genpd {
> + compatible = "xlnx,zynqmp-genpd";
What's the control interface for controlling the domains?
> +
> + pd_usb0: pd-usb0 {
> + pd-id = <22>;
> + #power-domain-cells = <0>;
There's no need for all these sub nodes. Make #power-domain-cells 1 and
put the id in the cell value.
> + };
> +
> + pd_sata: pd-sata {
> + pd-id = <28>;
> + #power-domain-cells = <0>;
> + };
> +
> + pd_gpu: pd-gpu {
> + pd-id = <58 20 21>;
> + #power-domain-cells = <0x0>;
> + };
> + };
> +
> + sata0: ahci at SATA_AHCI_HBA {
> + ...
> + power-domains = <&pd_sata>;
> + ...
> + };
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-03-05 22:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 23:55 [PATCH 0/2] drivers: soc: xilinx: Add support for ZynqMP power domain driver Jolly Shah
2018-02-27 23:55 ` [PATCH 1/2] dt-bindings: power: Add ZynqMP power domain bindings Jolly Shah
2018-03-05 22:39 ` Rob Herring [this message]
2018-03-06 7:59 ` Geert Uytterhoeven
2018-03-06 8:06 ` Marek Szyprowski
2018-03-15 17:47 ` Jolly Shah
2018-05-17 21:10 ` Jolly Shah
2018-05-18 6:30 ` Marek Szyprowski
2018-05-18 21:18 ` Jolly Shah
2018-07-20 16:57 ` Jolly Shah
2018-02-27 23:55 ` [PATCH 2/2] drivers: soc: xilinx: Add ZynqMP power domain driver Jolly Shah
2018-03-02 16:40 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180305223905.65nnunv63fyg7bye@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox