Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1256550

Re: [PATCH v3 18/27] mtd: nand: omap2: Implement NAND ready using gpiolib

From Boris Brezillon <boris.brezillon@free-electrons.com>
Newsgroups linux.kernel
Subject Re: [PATCH v3 18/27] mtd: nand: omap2: Implement NAND ready using gpiolib
Date 2015-10-27 09:20 +0100
Message-ID <qo7E7-2QQ-9@gated-at.bofh.it> (permalink)
References <qa5iO-5JO-13@gated-at.bofh.it> <qa5iQ-5JO-65@gated-at.bofh.it> <qnWSl-4rz-5@gated-at.bofh.it> <qo7up-2NF-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi Roger,

On Tue, 27 Oct 2015 10:03:02 +0200
Roger Quadros <rogerq@ti.com> wrote:

> On 26/10/15 22:49, Brian Norris wrote:
> > 
> > Others have been looking at using GPIOs for the ready/busy pin too. At a
> > minimum, we need an updated DT binding doc for this, since I see you're
> > adding this via device tree in a later patch (I don't see any DT binding
> > patch for this; but I could just be overlooking it). It'd also be great
> > if this support was moved to nand_dt_init() so other platforms can
> > benefit, but I won't require that.
> > 
> > Also, previous [0] proposers had suggested 'rb-gpios', not 'ready-gpio'
> > (the hardware docs typically call it 'rb' for ready/busy, FWIW). I don't
> > really care, but the name should be going into a doc, so we can choose
> > the same one everywhere.
> > 
> > EDIT: looks like the discussion was partly here [1] and it seems we're
> > landing on "rb-gpios" in the latest version [2]. Can we stick with that?
> 
> Why should it be "rb-gpios" and not "rb-gpio"?
> I don't think there are multiple gpios for r/b# function.

Because it's supposed to be a generic binding, and some NAND chips
embed several dies, thus exposing several CS and RB pins, hence the
rb-gpios name.
Also, as described here [1], the convention is to name your property
<name>-gpios even if you only need one gpio.

Best Regards,

Boris

[1]http://lxr.free-electrons.com/source/Documentation/devicetree/bindings/gpio/gpio.txt#L16



-- 
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
--
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/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH v3 18/27] mtd: nand: omap2: Implement NAND ready using  gpiolib Brian Norris <computersforpeace@gmail.com> - 2015-10-26 21:50 +0100
  Re: [PATCH v3 18/27] mtd: nand: omap2: Implement NAND ready using  gpiolib Roger Quadros <rogerq@ti.com> - 2015-10-27 09:10 +0100
    Re: [PATCH v3 18/27] mtd: nand: omap2: Implement NAND ready using  gpiolib Boris Brezillon <boris.brezillon@free-electrons.com> - 2015-10-27 09:20 +0100
      Re: [PATCH v3 18/27] mtd: nand: omap2: Implement NAND ready using  gpiolib Roger Quadros <rogerq@ti.com> - 2015-10-27 09:50 +0100
  Re: [PATCH v3 18/27] mtd: nand: omap2: Implement NAND ready using  gpiolib Boris Brezillon <boris.brezillon@free-electrons.com> - 2015-10-27 09:30 +0100

csiph-web