devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Baoyou Xie <baoyou.xie@linaro.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	catalin.marinas@arm.com, xie.baoyou@zte.com.cn,
	will.deacon@arm.com, linux-kernel@vger.kernel.org,
	robh+dt@kernel.org, chen.chaokai@zte.com.cn,
	viresh.kumar@linaro.org, wang.qiang01@zte.com.cn,
	jun.nie@linaro.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] arm64: dts: zx: add pcu_domain node for zx296718
Date: Mon, 5 Dec 2016 16:54:13 +0800	[thread overview]
Message-ID: <20161205085411.GB2749@dragon> (raw)
In-Reply-To: <1480925871-20855-1-git-send-email-baoyou.xie@linaro.org>

On Mon, Dec 05, 2016 at 04:17:51PM +0800, Baoyou Xie wrote:
> This patch adds the pcu_domain node, so it can be used
> by zte-soc's power domain driver.
> 
> Signed-off-by: Baoyou Xie <baoyou.xie@linaro.org>

I'm fine with the patch itself, but I need to wait the driver and
bindings being accepted to apply it.

Shawn

> ---
>  arch/arm64/boot/dts/zte/zx296718.dtsi | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/zte/zx296718.dtsi b/arch/arm64/boot/dts/zte/zx296718.dtsi
> index b44d1d1..1aa0587 100644
> --- a/arch/arm64/boot/dts/zte/zx296718.dtsi
> +++ b/arch/arm64/boot/dts/zte/zx296718.dtsi
> @@ -302,6 +302,11 @@
>  			reg = <0x116000 0x1000>;
>  		};
>  
> +		pcu_domain: pcu@117000 {
> +			compatible = "zte,zx296718-pcu";
> +			reg = <0x00117000 0x1000>;
> +		};
> +
>  		uart0: uart@11f000 {
>  			compatible = "arm,pl011", "arm,primecell";
>  			arm,primecell-periphid = <0x001feffe>;
> -- 
> 2.7.4
> 

      reply	other threads:[~2016-12-05  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05  8:17 [PATCH v2] arm64: dts: zx: add pcu_domain node for zx296718 Baoyou Xie
2016-12-05  8:54 ` Shawn Guo [this message]

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=20161205085411.GB2749@dragon \
    --to=shawnguo@kernel.org \
    --cc=baoyou.xie@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=chen.chaokai@zte.com.cn \
    --cc=devicetree@vger.kernel.org \
    --cc=jun.nie@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=wang.qiang01@zte.com.cn \
    --cc=will.deacon@arm.com \
    --cc=xie.baoyou@zte.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).