From mboxrd@z Thu Jan 1 00:00:00 1970 From: heiko@sntech.de (Heiko =?ISO-8859-1?Q?St=FCbner?=) Date: Mon, 14 Dec 2015 14:12:33 +0100 Subject: [PATCH 3/4] ARM: dts: rockchip: add eFuse node for rk3066a SoCs In-Reply-To: <3368238.OTPIyEf9PI@diego> References: <1447227272-1728-1-git-send-email-wxt@rock-chips.com> <566E926E.7090903@linaro.org> <3368238.OTPIyEf9PI@diego> Message-ID: <8067633.MgqW58IghF@diego> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Am Montag, 14. Dezember 2015, 14:06:06 schrieb Heiko St?bner: > 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. after looking at the patch-series as a whole, I just noticed, that they don't even depend on each other ... so I could've picked them earlier easily. Anyway, I'll do that now. > > 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 > > > --- > > > > > > 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 at 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 at 20038000 { > > > > > > compatible = "snps,dw-apb-timer-osc"; > > > reg = <0x20038000 0x100>;