Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757469Ab3HPWm4 (ORCPT ); Fri, 16 Aug 2013 18:42:56 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:55940 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751935Ab3HPWmw (ORCPT ); Fri, 16 Aug 2013 18:42:52 -0400 X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 72.84.113.162 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19nGruM2g3ZpwyzMim1LPdKlfVKKj9seJU= Date: Fri, 16 Aug 2013 15:50:46 -0400 From: Jason Cooper To: Sebastian Hesselbarth Cc: Rob Herring , Pawel Moll , Mark Rutland , Stephen Warren , Ian Campbell , Russell King , Andrew Lunn , Gregory Clement , Thomas Petazzoni , Arnd Bergmann , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [RFC v1 4/5] ARM: mvebu: add Armada 1500 and Sony NSZ-GS7 device tree files Message-ID: <20130816195046.GU13964@titan.lakedaemon.net> References: <1376682098-10580-1-git-send-email-sebastian.hesselbarth@gmail.com> <1376682098-10580-5-git-send-email-sebastian.hesselbarth@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1376682098-10580-5-git-send-email-sebastian.hesselbarth@gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2914 Lines: 69 On Fri, Aug 16, 2013 at 09:41:37PM +0200, Sebastian Hesselbarth wrote: > This adds very basic device tree files for the Marvell Armada 1500 SoC > and the Sony NSZ-GS7 GoogleTV board. Currently, SoC only has nodes for > cpus, some clocks, l2 cache controller, local timer, apb timers, uart, > and interrupt controllers. > > The clocks are fixed-clock placeholders until a real DT clock provider > is available. Cache controller node may be wrong and was just guessed > out of Armada 370 and GPL'd 1500 source. Timers except clocksource have > not really been tested. > > The separation into soc/apb and soc/sm-apb may be removed, but it looks > like Armada 1500 has a separate peripheral bus for the System Manager > core that can also been accessed by CPUs. (If you look closely on GTV > boot logs, you can see SM and CPU fighting for UART ;) ) > > The Sony NSZ-GS7 is a GoogleTV consumer device comprising the SoC above. > Since last week or so, there is a way to install a custom u-boot and > boot stock, unsigned kernels easily. Just ask Google about it, if you > are willing to void your warranty. > > Signed-off-by: Sebastian Hesselbarth > --- > Cc: Rob Herring > Cc: Pawel Moll > Cc: Mark Rutland > Cc: Stephen Warren > Cc: Ian Campbell > Cc: Russell King > Cc: Jason Cooper > Cc: Andrew Lunn > Cc: Gregory Clement > Cc: Thomas Petazzoni > Cc: Arnd Bergmann > Cc: devicetree@vger.kernel.org > Cc: linux-arm-kernel@lists.infradead.org > Cc: linux-kernel@vger.kernel.org > --- > arch/arm/boot/dts/Makefile | 3 +- > arch/arm/boot/dts/armada-1500-sony-nsz-gs7.dts | 29 +++ > arch/arm/boot/dts/armada-1500.dtsi | 225 ++++++++++++++++++++++++ > 3 files changed, 256 insertions(+), 1 deletion(-) > create mode 100644 arch/arm/boot/dts/armada-1500-sony-nsz-gs7.dts > create mode 100644 arch/arm/boot/dts/armada-1500.dtsi > > diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile > index 641b3c9..3186904 100644 > --- a/arch/arm/boot/dts/Makefile > +++ b/arch/arm/boot/dts/Makefile > @@ -103,7 +103,8 @@ dtb-$(CONFIG_ARCH_MVEBU) += armada-370-db.dtb \ > armada-370-rd.dtb \ > armada-xp-db.dtb \ > armada-xp-gp.dtb \ > - armada-xp-openblocks-ax3-4.dtb > + armada-xp-openblocks-ax3-4.dtb \ > + armada-1500-sony-nsz-gs7.dtb alphabetical. And now I need to pick up a googleTV... thx, Jason. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/