From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from muru.com ([72.249.23.125]) by bombadil.infradead.org with esmtp (Exim 4.80.1 #2 (Red Hat Linux)) id 1ZlnhB-0007b6-BW for linux-mtd@lists.infradead.org; Tue, 13 Oct 2015 00:44:02 +0000 Date: Mon, 12 Oct 2015 17:43:35 -0700 From: Tony Lindgren To: Roger Quadros Cc: dwmw2@infradead.org, computersforpeace@gmail.com, ezequiel@vanguardiasur.com.ar, javier@dowhile0.org, fcooper@ti.com, nsekhar@ti.com, linux-mtd@lists.infradead.org, linux-omap@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 27/27] ARM: dts: omap3: Fix gpmc and NAND nodes Message-ID: <20151013004335.GU23801@atomide.com> References: <1442588029-13769-1-git-send-email-rogerq@ti.com> <1442588029-13769-28-git-send-email-rogerq@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1442588029-13769-28-git-send-email-rogerq@ti.com> List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , * Roger Quadros [150918 08:00]: > Add compatible id, GPMC register resource and interrupt > resource to NAND controller nodes. > > The GPMC driver now implements gpiochip and irqchip so > enable gpio-controller and interrupt-controller properties. > > With this the interrupt parent of NAND node changes so fix it > accordingly. ... > --- a/arch/arm/boot/dts/logicpd-torpedo-som.dtsi > +++ b/arch/arm/boot/dts/logicpd-torpedo-som.dtsi > @@ -35,11 +35,14 @@ > }; > > &gpmc { > - ranges = <0 0 0x00000000 0x1000000>; /* CS0: 16MB for NAND */ > + ranges = <0 0 0x08000000 0x1000000>; /* CS0: 16MB for NAND */ > > nand@0,0 { > - linux,mtd-name = "micron,mt29f4g16abbda3w"; > + compatible = "ti,omap2-nand"; > reg = <0 0 4>; /* CS0, offset 0, IO size 4 */ > + interrupt-parent = <&intc>; > + interrupts = <20>; > + linux,mtd-name = "micron,mt29f4g16abbda3w"; > nand-bus-width = <16>; > ti,nand-ecc-opt = "bch8"; > gpmc,sync-clk-ps = <0>; At least torpedo breaks for NFSroot as NAND now overlaps with Ethernet.. What's the policy you have for moving the addresses around? There may be other similar cases to check too. Regards, Tony