From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nand: stm_nand_bch: add new driver
Date: Wed, 9 Jul 2014 10:22:29 -0700 [thread overview]
Message-ID: <20140709172229.GH7537@ld-irv-0074> (raw)
In-Reply-To: <20140708095855.29c2fb87@bbrezillon>
Hi Boris,
On Tue, Jul 08, 2014 at 09:58:55AM +0200, Boris BREZILLON wrote:
> On Mon, 7 Jul 2014 16:52:22 -0700 Brian Norris <computersforpeace@gmail.com> wrote:
> > 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:
> > >
> > > 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
Yes, please send 1 and 2 on their own. I think that would be a good
start for supporting these drivers.
Brian
next prev parent reply other threads:[~2014-07-09 17:22 UTC|newest]
Thread overview: 15+ 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
[not found] ` <20140703100522.756f9715@bbrezillon>
2014-07-07 23:52 ` Brian Norris
[not found] ` <20140708095855.29c2fb87@bbrezillon>
2014-07-09 17:22 ` Brian Norris [this message]
[not found] ` <20980858CB6D3A4BAE95CA194937D5E73EAFAFF1@DBDE04.ent.ti.com>
2014-07-08 0:16 ` Brian Norris
2014-08-05 14:23 ` Lee Jones
2014-08-05 21:02 ` pekon at pek-sem.com
2014-08-19 2:12 ` Brian Norris
2014-08-20 18:02 ` pekon
2014-08-06 10:26 ` Lee Jones
[not found] ` <20140731164709.GK9030@lee--X1>
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-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=20140709172229.GH7537@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=linux-arm-kernel@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