From: Jamie Iles <jamie@jamieiles.com>
To: Scott Wood <scottwood@freescale.com>
Cc: Jamie Iles <jamie@jamieiles.com>,
devicetree-discuss@lists.ozlabs.org,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH] mtd: gpio-nand: add device tree bindings
Date: Wed, 27 Jul 2011 20:55:12 +0100 [thread overview]
Message-ID: <20110727195512.GC3001@gallagher> (raw)
In-Reply-To: <20110727144501.7e0420cd@schlenkerla.am.freescale.net>
Hmm, get_maintainer.pl got Artem's address wrong (old Nokia address) for
gpio-nand.c so correct one on CC now!
On Wed, Jul 27, 2011 at 02:45:01PM -0500, Scott Wood wrote:
> On Wed, 27 Jul 2011 15:03:30 +0100
> Jamie Iles <jamie@jamieiles.com> wrote:
>
> > diff --git a/Documentation/devicetree/bindings/mtd/gpio-nand.txt b/Documentation/devicetree/bindings/mtd/gpio-nand.txt
> > new file mode 100644
> > index 0000000..98cb152
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/mtd/gpio-nand.txt
> > @@ -0,0 +1,43 @@
> > +GPIO assisted NAND flash
> > +
> > +Required properties:
> > +- compatible : "gpio-nand"
> > +- reg : should specify localbus chip select and size used for the chip. For
> > + ARM platforms where a dummy read is needed to provide synchronisation with
> > + regards to bus reordering, an optional second resource describes the
> > + location to read from.
>
> I don't see how a pure "gpio nand" device would have any memory mapped
> I/O. I think you need a more specific compatible for this.
OK, fair point. I'm not sure what a better name would be though, maybe
gpio-assisted-nand?
> > +Optional properties:
> > +- bank-width : Width (in bytes) of the bank. Equal to the device width times
> > + the number of interleaved chips.
>
> Interleaved NAND chips? Is that actually done?
Doh, that shouldn't read like that. It's really just the bank width.
> > +Examples:
> > +
> > +gpio-nand@1,0 {
> > + compatible = "gpio-nand";
> > + reg = <1 0x0000 0x1000>;
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + gpios = <&banka 1 0 /* rdy */
> > + &banka 2 0 /* nce */
> > + &banka 3 0 /* ale */
> > + &banka 4 0 /* cle */
> > + 0 /* nwp */>;
> > +
> > + flash {
> > + #address-cells = <1>;
> > + #size-cells = <1>;
> > + compatible = "...";
> > +
> > + partition@0 {
> > + ...
> > + };
> > + };
> > +};
>
> Here you have a separate flash node underneath the gpio-nand node, but
> earlier in the patch comment you show the partitions being directly under
> gpio-nand, and from a quick glance it appears the latter is what the code
> supports.
Yes, that's definitely wrong! The partitions should be directly under the
nand controller node.
Thanks for the review!
Jamie
next prev parent reply other threads:[~2011-07-27 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 14:03 [PATCH] mtd: gpio-nand: add device tree bindings Jamie Iles
2011-07-27 19:45 ` Scott Wood
2011-07-27 19:55 ` Jamie Iles [this message]
2011-07-27 21:01 ` Scott Wood
2011-07-28 0:06 ` Mike Frysinger
2011-07-28 0:07 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2011-12-18 10:00 Jamie Iles
2011-12-18 11:55 ` Artem Bityutskiy
2011-12-21 20:52 ` Artem Bityutskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110727195512.GC3001@gallagher \
--to=jamie@jamieiles.com \
--cc=dedekind1@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=scottwood@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox