From: Scott Wood <scottwood@freescale.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
David Woodhouse <dwmw2@infradead.org>,
devicetree-discuss@lists.ozlabs.org,
linux-mtd@lists.infradead.org,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCHv4] mtd: gpio-nand: add device tree bindings
Date: Wed, 10 Aug 2011 10:13:27 -0500 [thread overview]
Message-ID: <4E42A017.7040608@freescale.com> (raw)
In-Reply-To: <1312902747-21372-1-git-send-email-jamie@jamieiles.com>
On 08/09/2011 10:12 AM, Jamie Iles wrote:
> +Optional properties:
> +- bank-width : Width (in bytes) of the device. If not present, the width
> + defaults to 8 bits.
"in bytes" versus "defaults to 8 bits"...
> +- chip-delay : chip dependent delay for transferring data from array to
> + read registers (tR). If not present then a default of 0 is used.
nand_set_defaults() will set this to 20 us if you pass in zero.
> +- gpio-control-nand,io-sync-reg : A 64-bit physical address for a read
> + location used to guard against bus reordering with regards to accesses to
> + the GPIO's and the NAND flash data bus. If present, then after changing
> + GPIO state, this register will be read to ensure that the accesses have
> + completed.
The driver does it before and after all cmd_ctrl byte writes, in
addition to after changing the GPIO state.
-Scott
next prev parent reply other threads:[~2011-08-10 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 15:12 [PATCHv4] mtd: gpio-nand: add device tree bindings Jamie Iles
2011-08-10 15:13 ` Scott Wood [this message]
2011-08-11 9:00 ` Jamie Iles
2011-08-15 13:57 ` Artem Bityutskiy
2011-08-15 13:58 ` Jamie Iles
2011-08-15 14:28 ` Artem Bityutskiy
2011-08-15 14:38 ` Jamie Iles
2011-08-15 14:45 ` Artem Bityutskiy
2011-08-15 15:24 ` Jamie Iles
2011-08-19 19:51 ` Artem Bityutskiy
2011-08-19 21:18 ` Jamie Iles
2011-08-20 3:39 ` Artem Bityutskiy
2011-08-20 6:38 ` Jamie Iles
2011-08-20 12:09 ` 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=4E42A017.7040608@freescale.com \
--to=scottwood@freescale.com \
--cc=dedekind1@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dwmw2@infradead.org \
--cc=grant.likely@secretlab.ca \
--cc=jamie@jamieiles.com \
--cc=linux-mtd@lists.infradead.org \
/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