From: Boris BREZILLON <boris.brezillon@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: devicetree@vger.kernel.org,
Boris BREZILLON <b.brezillon.dev@gmail.com>,
kernel@stlinux.com, linux-kernel@vger.kernel.org,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
linux-mtd@lists.infradead.org, "Gupta, Pekon\"" <pekon@ti.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Lee Jones <lee.jones@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mtd: nand: stm_nand_bch: add new driver
Date: Tue, 8 Jul 2014 09:58:55 +0200 [thread overview]
Message-ID: <20140708095855.29c2fb87@bbrezillon> (raw)
In-Reply-To: <20140707235222.GC7537@ld-irv-0074>
Hi Brian,
On Mon, 7 Jul 2014 16:52:22 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
> Hi Boris,
>
> On Thu, Jul 03, 2014 at 10:05:22AM +0200, Boris BREZILLON wrote:
> > On Wed, 2 Jul 2014 17:22:37 -0700 Brian Norris <computersforpeace@gmail.com> wrote:
> > > On Wed, May 28, 2014 at 10:20:05AM +0100, Lee Jones wrote:
> > > > +
> > > > + nand_timing0: nand-timing {
> > > > + sig-setup = <10>;
> > > > + sig-hold = <10>;
> > > > + CE-deassert = <0>;
> > > > + WE-to-RBn = <100>;
> > > > + wr-on = <10>;
> > > > + wr-off = <30>;
> > > > + rd-on = <10>;
> > > > + rd-off = <30>;
> > > > + chip-delay = <30>; /* delay in us */
> > > > + };
> > >
> > > You didn't document any of this node. And I don't think we want to
> > > specify every single timing parameter in DT; it may make sense to use
> > > Boris Brezillon's approach (I note this further down, in the driver
> > > code) for mapping non-ONFI NAND timings into a compatible ONFI timing
> > > mode. This will greatly simplify the bindings needed, since it's
> > > standardized and auto-detectable in many cases.
> >
> >
> > AFAIR, the NAND timing representation for non-ONFI chips question was
> > left unanswered:
> >
> > https://lkml.org/lkml/2014/5/20/581
> >
> > I can definitely respin my NAND timings series, but I'd like to be sure
> > this is how you want it done before doing so.
>
> Can we start by supporting ONFI-only (or ONFI-only, plus entries in
> nand_flash_ids[]), and have nand_base provide the translation so drivers
> can retrieve the info? Then we can begin supporting new drivers like
> Lee's, and worry about the DT question separately.
So, basically, I just send a new series with patch 1 and 2 from my sunxi
NAND series [1] (including the fixes you suggested, of course), right ?
[1] http://thread.gmane.org/gmane.comp.hardware.netbook.arm.sunxi/7977
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-08 7:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 9:20 [PATCH] mtd: nand: stm_nand_bch: add new driver Lee Jones
2014-07-03 0:22 ` Brian Norris
2014-07-03 8:05 ` Boris BREZILLON
2014-07-07 23:52 ` Brian Norris
2014-07-08 7:58 ` Boris BREZILLON [this message]
2014-07-09 17:22 ` Brian Norris
2014-07-03 9:09 ` Gupta, Pekon
2014-07-08 0:16 ` Brian Norris
2014-08-05 14:23 ` Lee Jones
2014-08-05 21:02 ` pekon
2014-08-19 2:12 ` Brian Norris
2014-08-20 18:02 ` pekon
2014-07-31 16:47 ` Lee Jones
2014-07-31 17:54 ` Brian Norris
2014-08-01 9:27 ` Lee Jones
2014-08-19 2:42 ` Brian Norris
2014-08-06 10:44 ` Lee Jones
2014-08-06 10:26 ` Lee Jones
2014-07-03 0:50 ` Brian Norris
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=20140708095855.29c2fb87@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=b.brezillon.dev@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.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;
as well as URLs for NNTP newsgroup(s).