From: Heiko Stuebner <heiko@sntech.de>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: wxt@rock-chips.com, linux-arm-kernel@lists.infradead.org,
huangtao@rock-chips.com, zyw@rock-chips.com, xxx@rock-chips.com,
jay.xu@rock-chips.com, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 6/6] dt/bindings: rockchip: modify document of Rockchip power domains
Date: Fri, 19 Feb 2016 00:52:19 +0100 [thread overview]
Message-ID: <2204493.j28NF0gtji@phil> (raw)
In-Reply-To: <1455764899-13028-1-git-send-email-zhangqing@rock-chips.com>
Am Donnerstag, 18. Februar 2016, 11:08:19 schrieb Elaine Zhang:
> Add binding documentation for the power domains
> found on Rockchip RK3399 SoCs
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
This patch should probably include the devicetree people
Rob Herring <robh+dt@kernel.org>
Pawel Moll <pawel.moll@arm.com>
Mark Rutland <mark.rutland@arm.com>
Ian Campbell <ijc+devicetree@hellion.org.uk>
Kumar Gala <galak@codeaurora.org>
devicetree@vger.kernel.org
> ---
> .../bindings/soc/rockchip/power_domain.txt | 21
> +++++++++++++++++++++ 1 file changed, 21 insertions(+)
>
> diff --git
> a/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt
> b/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt index
> 13dc6a3..c65d401 100644
> --- a/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt
> +++ b/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt
> @@ -7,6 +7,7 @@ Required properties for power domain controller:
> - compatible: Should be one of the following.
> "rockchip,rk3288-power-controller" - for RK3288 SoCs.
> "rockchip,rk3368-power-controller" - for RK3368 SoCs.
> + "rockchip,rk3399-power-controller" - for RK3399 SoCs.
> - #power-domain-cells: Number of cells in a power-domain specifier.
> Should be 1 for multiple PM domains.
> - #address-cells: Should be 1.
> @@ -16,6 +17,7 @@ Required properties for power domain sub nodes:
> - reg: index of the power domain, should use macros in:
> "include/dt-bindings/power/rk3288-power.h" - for RK3288 type power
> domain. "include/dt-bindings/power/rk3368-power.h" - for RK3368 type
> power domain. + "include/dt-bindings/power/rk3399-power.h" - for RK3399
> type power domain. - clocks (optional): phandles to clocks which need to
> be enabled while power domain switches state.
>
> @@ -45,12 +47,25 @@ Example:
> };
> };
>
> + power: power-controller {
> + compatible = "rockchip,rk3399-power-controller";
> + #power-domain-cells = <1>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pd_gpu {
> + reg = <RK3399_PD_GPU>;
> + clocks = <&cru ACLK_GPU>;
> + };
> + };
> +
I don't think we need to add another example for every type of power-domain controller :-) .
> Node of a device using power domains must have a power-domains property,
> containing a phandle to the power device node and an index specifying
> which power domain to use.
> The index should use macros in:
> "include/dt-bindings/power/rk3288-power.h" - for rk3288 type power
> domain. "include/dt-bindings/power/rk3368-power.h" - for rk3368 type
> power domain. + "include/dt-bindings/power/rk3399-power.h" - for rk3399
> type power domain.
>
> Example of the node using power domain:
>
> @@ -65,3 +80,9 @@ Example of the node using power domain:
> power-domains = <&power RK3368_PD_GPU_1>;
> /* ... */
> };
> +
> + node {
> + /* ... */
> + power-domains = <&power RK3399_PD_GPU>;
> + /* ... */
> + };
same here
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 6/6] dt/bindings: rockchip: modify document of Rockchip power domains
Date: Fri, 19 Feb 2016 00:52:19 +0100 [thread overview]
Message-ID: <2204493.j28NF0gtji@phil> (raw)
In-Reply-To: <1455764899-13028-1-git-send-email-zhangqing@rock-chips.com>
Am Donnerstag, 18. Februar 2016, 11:08:19 schrieb Elaine Zhang:
> Add binding documentation for the power domains
> found on Rockchip RK3399 SoCs
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
This patch should probably include the devicetree people
Rob Herring <robh+dt@kernel.org>
Pawel Moll <pawel.moll@arm.com>
Mark Rutland <mark.rutland@arm.com>
Ian Campbell <ijc+devicetree@hellion.org.uk>
Kumar Gala <galak@codeaurora.org>
devicetree at vger.kernel.org
> ---
> .../bindings/soc/rockchip/power_domain.txt | 21
> +++++++++++++++++++++ 1 file changed, 21 insertions(+)
>
> diff --git
> a/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt
> b/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt index
> 13dc6a3..c65d401 100644
> --- a/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt
> +++ b/Documentation/devicetree/bindings/soc/rockchip/power_domain.txt
> @@ -7,6 +7,7 @@ Required properties for power domain controller:
> - compatible: Should be one of the following.
> "rockchip,rk3288-power-controller" - for RK3288 SoCs.
> "rockchip,rk3368-power-controller" - for RK3368 SoCs.
> + "rockchip,rk3399-power-controller" - for RK3399 SoCs.
> - #power-domain-cells: Number of cells in a power-domain specifier.
> Should be 1 for multiple PM domains.
> - #address-cells: Should be 1.
> @@ -16,6 +17,7 @@ Required properties for power domain sub nodes:
> - reg: index of the power domain, should use macros in:
> "include/dt-bindings/power/rk3288-power.h" - for RK3288 type power
> domain. "include/dt-bindings/power/rk3368-power.h" - for RK3368 type
> power domain. + "include/dt-bindings/power/rk3399-power.h" - for RK3399
> type power domain. - clocks (optional): phandles to clocks which need to
> be enabled while power domain switches state.
>
> @@ -45,12 +47,25 @@ Example:
> };
> };
>
> + power: power-controller {
> + compatible = "rockchip,rk3399-power-controller";
> + #power-domain-cells = <1>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pd_gpu {
> + reg = <RK3399_PD_GPU>;
> + clocks = <&cru ACLK_GPU>;
> + };
> + };
> +
I don't think we need to add another example for every type of power-domain controller :-) .
> Node of a device using power domains must have a power-domains property,
> containing a phandle to the power device node and an index specifying
> which power domain to use.
> The index should use macros in:
> "include/dt-bindings/power/rk3288-power.h" - for rk3288 type power
> domain. "include/dt-bindings/power/rk3368-power.h" - for rk3368 type
> power domain. + "include/dt-bindings/power/rk3399-power.h" - for rk3399
> type power domain.
>
> Example of the node using power domain:
>
> @@ -65,3 +80,9 @@ Example of the node using power domain:
> power-domains = <&power RK3368_PD_GPU_1>;
> /* ... */
> };
> +
> + node {
> + /* ... */
> + power-domains = <&power RK3399_PD_GPU>;
> + /* ... */
> + };
same here
Heiko
next prev parent reply other threads:[~2016-02-18 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 3:08 [PATCH v2 6/6] dt/bindings: rockchip: modify document of Rockchip power domains Elaine Zhang
2016-02-18 3:08 ` Elaine Zhang
2016-02-18 23:52 ` Heiko Stuebner [this message]
2016-02-18 23:52 ` Heiko Stuebner
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=2204493.j28NF0gtji@phil \
--to=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=jay.xu@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=wxt@rock-chips.com \
--cc=xxx@rock-chips.com \
--cc=zhangqing@rock-chips.com \
--cc=zyw@rock-chips.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.