From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [PATCH v8 5/5] ARM: OMAP: gpmc: add DT bindings for GPMC timings and NAND Date: Tue, 15 Jan 2013 10:03:24 -0800 Message-ID: <20130115180324.GZ14149@atomide.com> References: <1355481404-27695-1-git-send-email-zonque@gmail.com> <1355481404-27695-6-git-send-email-zonque@gmail.com> <20130114180602.GV14149@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org To: Daniel Mack Cc: Paul Walmsley , x0148406@ti.com, Enric Balletbo Serra , devicetree-discuss@lists.ozlabs.org, nsekhar@ti.com, avinashphilip@ti.com, jon-hunter@ti.com, rob.herring@calxeda.com, Javier Martinez Canillas , linux-arm-kernel@lists.infradead.org, Ezequiel Garcia , jacmet@sunsite.dk, grant.likely@secretlab.ca, linux-omap@vger.kernel.org List-Id: devicetree@vger.kernel.org * Daniel Mack [130114 15:30]: > On Jan 15, 2013 2:06 AM, "Tony Lindgren" wrote: > > > > * Ezequiel Garcia [121223 13:49]: > > > On Fri, Dec 14, 2012 at 7:36 AM, Daniel Mack wrote: > > > > + > > > > +Example for an AM33xx board: > > > > + > > > > + gpmc: gpmc@50000000 { > > > > + compatible = "ti,am3352-gpmc"; > > > > + ti,hwmods = "gpmc"; > > > > + reg = <0x50000000 0x1000000>; > > > > + interrupts = <100>; > > > > + gpmc,num-cs = <8>; > > > > + gpmc,num-waitpins = <2>; > > > > + #address-cells = <2>; > > > > + #size-cells = <1>; > > > > + ranges = <0 0 0x08000000 0x2000>; /* CS0: NAND > */ > > > > + > > > > + nand@0,0 { > > > > + reg = <0 0 0>; /* CS0, offset 0 */ > > > > > > I'm a bit confused by this: what are the other two values in "reg"? > > > I see you've only added a binding for CS. > > > > > > I've extended a bit on your work and added a binding to enable OneNAND > > > device on my IGEP board. > > > > > > I might send some patches in case anyone wants to give it a try. > > > > Daniel, should this be updated to just pass the CS? > > No, as Rob pointed out earlier in a thread about this topic, the 'ranges' > feature will help doing the math for the offset calculation eventually, so > we need to pass all three values. OK thanks. Applying this set into omap-for-v3.9/gpmc. Also sounds like Ezequiel needs to update his follow up patches accordingly. Regards, Tony