From: Ezequiel Garcia <ezequiel.garcia@imgtec.com>
To: bpqw <bpqw@micron.com>,
Brian Norris <computersforpeace@gmail.com>,
"arnaud.mouiche@invoxia.com" <arnaud.mouiche@invoxia.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: "ionela.voinescu@imgtec.com" <ionela.voinescu@imgtec.com>
Subject: Re: [PATCH 0/2] staging: mtd: Support for GigaDevice SPI NAND flash
Date: Thu, 20 Nov 2014 10:18:20 -0300 [thread overview]
Message-ID: <546DEA1C.2080805@imgtec.com> (raw)
In-Reply-To: <71CF8D7F32C5C24C9CD1D0E02D52498A7713208B@NTXXIAMBX02.xacn.micron.com>
On 11/20/2014 05:39 AM, bpqw wrote:
> Hi Brian, Arnaud:
>> If we are going to a specific spinand framework, my advice would be to
>> read again the spi nor framework carefully first, and do something
>> similar (especially for latests work on quad spi)
>
> I think above idea is good.
> SPI NAND interface and command protocol are similar with SPI NOR, we can
> create a SPI NAND folder with similar framework with SPI NOR. But need to duplicate
> nand_bbt and nand_bch code into this folder due to SPI NAND still need BBM and ECC.
> How do you think?
>
Hm, perhaps it's better to rely in the NAND core code and avoid that BBT
and ECC code handling duplication?
Ionela and I are preparing an SPI NAND framework, but it's far from
ready yet, so if you have something to submit, please do so :)
Thanks,
--
Ezequiel
next prev parent reply other threads:[~2014-11-20 13:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 8:39 [PATCH 0/2] staging: mtd: Support for GigaDevice SPI NAND flash bpqw
2014-11-20 13:18 ` Ezequiel Garcia [this message]
2014-11-25 7:02 ` bpqw
2014-11-25 16:59 ` Ezequiel Garcia
[not found] <mailman.22397.1416508326.22890.linux-mtd@lists.infradead.org>
2014-11-21 1:16 ` Qi Wang 王起 (qiwang)
2014-11-21 9:24 ` arnaud.mouiche
2014-11-21 11:51 ` Ezequiel Garcia
-- strict thread matches above, loose matches on Subject: below --
2014-11-06 15:51 Ionela Voinescu
2014-11-06 16:05 ` Greg KH
2014-11-06 17:32 ` Ionela Voinescu
2014-11-06 17:44 ` Greg KH
2014-11-06 18:03 ` Ionela Voinescu
2014-11-06 18:17 ` Ezequiel Garcia
2014-11-06 19:20 ` Brian Norris
2014-11-07 13:00 ` Ionela Voinescu
2014-11-10 9:00 ` arnaud.mouiche
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=546DEA1C.2080805@imgtec.com \
--to=ezequiel.garcia@imgtec.com \
--cc=arnaud.mouiche@invoxia.com \
--cc=bpqw@micron.com \
--cc=computersforpeace@gmail.com \
--cc=ionela.voinescu@imgtec.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;
as well as URLs for NNTP newsgroup(s).