From: Ezequiel Garcia <ezequiel.garcia@imgtec.com>
To: "\"Qi Wang 王起 (qiwang)\"" <qiwang@micron.com>,
"Brian Norris" <computersforpeace@gmail.com>
Cc: "Ionela Voinescu" <ionela.voinescu@imgtec.com>,
"\"Frank Liu 刘群 (frankliu)\"" <frankliu@micron.com>,
"Andrew Bresticker" <abrestic@chromium.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"arnaud.mouiche@invoxia.com" <arnaud.mouiche@invoxia.com>,
"James Hartley" <james.hartley@imgtec.com>,
"\"Peter Pan 潘栋 (peterpandong)\"" <peterpandong@micron.com>
Subject: Re: [PATCH 0/6] SPI NAND for everyone
Date: Wed, 7 Jan 2015 09:13:40 -0300 [thread overview]
Message-ID: <54AD22F4.9020202@imgtec.com> (raw)
In-Reply-To: <71CF8D7F32C5C24C9CD1D0E02D52498A7714D979@NTXXIAMBX02.xacn.micron.com>
On 01/06/2015 09:55 PM, Qi Wang 王起 (qiwang) wrote:
> Hi Brian and Ezequiel,
>
> On 01/07/2015 5:03 AM, Ezequiel Garcia wrote:
>>
>>
>> On 01/06/2015 12:30 AM, Brian Norris wrote:
>>
>>>> The SPI NAND framework allows devices to register as NAND drivers. This
>> is
>>>> useful to take advantage of the bad block management code.
>>>
>>> I'm not so sure about this choice, but then I'm not so sure about the
>>> alternatives earlier. I understand that you and Qi Wang might have had
>>> some discussion off-list (please feel free to fill me and others in
>>> here, and I can add my thoughts).
>>>
>>
>> Indeed, I believe Qi Wang have these same concerns.
>
> Yes, I also consider this a lot. Actually, I already complete a new SPI NAND
> Framework to implement SPI NAND code independent with Parallel NAND.
> Testing on Micron Device is finished, my colleague will send out this
> patch to community soon for both you review.
>
Great!
However, I don't think it's a good plan to delay its submission. At this
stage we won't care about the little details, but we are mostly
interested in seeing and discussing the overall approach.
That will allow us to start the discussion earlier.
We'll worry about properly testing it and polishing it later.
"Release early, release often".
--
Ezequiel
prev parent reply other threads:[~2015-01-07 12:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 12:58 [PATCH 0/6] SPI NAND for everyone Ezequiel Garcia
2014-12-02 12:58 ` [PATCH 1/6] mtd: nand: Check length of ID before reading bits per cell Ezequiel Garcia
2014-12-13 0:51 ` Daniel Ehrenberg
2015-01-05 20:38 ` Brian Norris
2014-12-02 12:58 ` [PATCH 2/6] mtd: nand: Add JEDEC manufacturer ID for Gigadevice Ezequiel Garcia
2014-12-13 0:49 ` Daniel Ehrenberg
2015-04-21 23:04 ` Ezequiel Garcia
2015-04-22 17:47 ` Brian Norris
2014-12-02 12:58 ` [PATCH 3/6] mtd: nand: Allow to set a per-device ECC layout Ezequiel Garcia
2014-12-13 0:34 ` Daniel Ehrenberg
2014-12-02 12:58 ` [PATCH 4/6] mtd: Introduce SPI NAND framework Ezequiel Garcia
2014-12-15 21:18 ` Daniel Ehrenberg
2014-12-16 0:08 ` Ezequiel Garcia
[not found] ` <87F60714EC601C4C83DFF1D2E3D390A049EE77@NTXXIAMBX02.xacn.micron.com>
2014-12-22 4:34 ` Qi Wang 王起 (qiwang)
2014-12-22 15:44 ` Ezequiel Garcia
2015-01-05 20:47 ` Brian Norris
2014-12-02 12:58 ` [PATCH 5/6] mtd: spi-nand: Add devicetree binding Ezequiel Garcia
2014-12-13 1:27 ` Daniel Ehrenberg
2014-12-02 12:58 ` [PATCH 6/6] mtd: spi-nand: Support common SPI NAND devices Ezequiel Garcia
2014-12-13 1:27 ` Daniel Ehrenberg
2014-12-15 19:36 ` Ezequiel Garcia
2014-12-15 20:17 ` Daniel Ehrenberg
[not found] ` <87F60714EC601C4C83DFF1D2E3D390A049EE65@NTXXIAMBX02.xacn.micron.com>
2014-12-22 4:34 ` Qi Wang 王起 (qiwang)
2014-12-22 16:16 ` Ezequiel Garcia
2014-12-10 17:41 ` [PATCH 0/6] SPI NAND for everyone Ezequiel Garcia
2015-01-06 3:30 ` Brian Norris
2015-01-06 21:03 ` Ezequiel Garcia
2015-01-07 0:55 ` Qi Wang 王起 (qiwang)
2015-01-07 12:13 ` Ezequiel Garcia [this message]
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=54AD22F4.9020202@imgtec.com \
--to=ezequiel.garcia@imgtec.com \
--cc=abrestic@chromium.org \
--cc=arnaud.mouiche@invoxia.com \
--cc=computersforpeace@gmail.com \
--cc=frankliu@micron.com \
--cc=ionela.voinescu@imgtec.com \
--cc=james.hartley@imgtec.com \
--cc=linux-mtd@lists.infradead.org \
--cc=peterpandong@micron.com \
--cc=qiwang@micron.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).