From: "Heiko Stübner" <heiko@sntech.de>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Caesar Wang <wxt@rock-chips.com>,
linux-rockchip@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
devicetree@vger.kernel.org, Kumar Gala <galak@codeaurora.org>,
linux-kernel@vger.kernel.org,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/4] ARM: dts: rockchip: add eFuse node for rk3066a SoCs
Date: Mon, 14 Dec 2015 14:06:06 +0100 [thread overview]
Message-ID: <3368238.OTPIyEf9PI@diego> (raw)
In-Reply-To: <566E926E.7090903@linaro.org>
Hi srini,
Am Montag, 14. Dezember 2015, 09:57:02 schrieb Srinivas Kandagatla:
> Heiko,
>
> Can you take the DT patches in this series via your tree.
>
> I picked up nvmem patches from this series.
yep that was my plan ... just needed to wait for the nvmem parts to be picked.
Thanks for the notifying me :-)
Heiko
>
> thanks,
> srini
>
> On 11/11/15 07:34, Caesar Wang wrote:
> > This patch add the eFuse dt node for rk3066a SoCs.
> >
> > Signed-off-by: Caesar Wang <wxt@rock-chips.com>
> > ---
> >
> > arch/arm/boot/dts/rk3066a.dtsi | 13 +++++++++++++
> > 1 file changed, 13 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/rk3066a.dtsi
> > b/arch/arm/boot/dts/rk3066a.dtsi index 946f187..f61bb8a 100644
> > --- a/arch/arm/boot/dts/rk3066a.dtsi
> > +++ b/arch/arm/boot/dts/rk3066a.dtsi
> > @@ -153,6 +153,19 @@
> >
> > clock-names = "timer", "pclk";
> >
> > };
> >
> > + efuse: efuse@20010000 {
> > + compatible = "rockchip,rockchip-efuse";
> > + reg = <0x20010000 0x4000>;
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + clocks = <&cru PCLK_EFUSE>;
> > + clock-names = "pclk_efuse";
> > +
> > + cpu_leakage: cpu_leakage {
> > + reg = <0x17 0x1>;
> > + };
> > + };
> > +
> >
> > timer@20038000 {
> >
> > compatible = "snps,dw-apb-timer-osc";
> > reg = <0x20038000 0x100>;
next prev parent reply other threads:[~2015-12-14 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 7:34 [PATCH 0/4] support the efuse for rk3188/rk3066a SoCs and cleanup driver on nvmem Caesar Wang
[not found] ` <1447227272-1728-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-11-11 7:34 ` [PATCH 3/4] ARM: dts: rockchip: add eFuse node for rk3066a SoCs Caesar Wang
[not found] ` <1447227272-1728-4-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2015-12-14 9:57 ` Srinivas Kandagatla
2015-12-14 13:06 ` Heiko Stübner [this message]
2015-12-14 13:12 ` Heiko Stübner
2015-11-11 7:34 ` [PATCH 4/4] ARM: dts: rockchip: add eFuse node for rk3188 SoCs Caesar Wang
2015-12-02 2:44 ` [PATCH 0/4] support the efuse for rk3188/rk3066a SoCs and cleanup driver on nvmem Caesar Wang
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=3368238.OTPIyEf9PI@diego \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=wxt@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 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).