[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160307103855.57720146@bbrezillon>
Date: Mon, 7 Mar 2016 10:38:55 +0100
From: Boris Brezillon <boris.brezillon@...e-electrons.com>
To: Roger Quadros <rogerq@...com>
Cc: <tony@...mide.com>, <computersforpeace@...il.com>,
devicetree@...r.kernel.org, nsekhar@...com,
linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org,
ezequiel@...guardiasur.com.ar, javier@...hile0.org,
linux-omap@...r.kernel.org, dwmw2@...radead.org, fcooper@...com
Subject: Re: [PATCH v5 13/26] memory: omap-gpmc: Support general purpose
input for WAITPINs
On Mon, 7 Mar 2016 10:34:40 +0100
Boris Brezillon <boris.brezillon@...e-electrons.com> wrote:
> Hi Roger,
>
> On Fri, 19 Feb 2016 23:15:35 +0200
> Roger Quadros <rogerq@...com> wrote:
>
> > OMAPs can have 2 to 4 WAITPINs that can be used as general purpose
> > input if not used for memory wait state insertion.
> >
> > The first user will be the OMAP NAND chip to get the NAND
> > read/busy status using gpiolib.
>
> Just a comment on this approach. Why do you need to exposed native R/B
> pins as GPIOs? I mean, other NAND controllers are supporting R/B
> detection using dedicated logic, and they do not exposed those pins a
> plain GPIOs. Have you considered adding another property (rb-native ?)
Just had a look at the sunxi-nand binding, and we chose "allwinner,rb"
for this native RB logic. So "ti,rb" would be the equivalent for the
gpmc driver.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
Powered by blists - more mailing lists