From: "arnaud.mouiche@gmail.com" <arnaud.mouiche@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/2] staging: mtd: Support for GigaDevice SPI NAND flash
Date: Fri, 21 Nov 2014 10:24:47 +0100 [thread overview]
Message-ID: <546F04DF.4010501@gmail.com> (raw)
In-Reply-To: <71CF8D7F32C5C24C9CD1D0E02D52498A7713225E@NTXXIAMBX02.xacn.micron.com>
Le 21/11/2014 02:16, Qi Wang 王起 (qiwang) a écrit :
>> On 11/20/2014 10:18 AM, Ezequiel Garcia wrote:
>> Hm, perhaps it's better to rely in the NAND core code and avoid that BBT
>> and ECC code handling duplication?
If it means using the framework from drivers/mtd/nand directory, no,
definitely not.
This framework rely on common things that every raw nand devices are
sharing, and on nand controllers from the SOC side.
That was my first attempt when looking for a spinand driver, but I
quickly switch to
>>
>> 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 :)
> Yes, duplicate BBT and ECC code from nand code do is not a good idea.
> But SPI NAND framework should be a standalone module in MTD, might cause
> chaos if it still rely on NAND core code, that is my only concern.
> How do you think?
The ideal way to do should be to factorize the BBT for nand / onenand /
spinand, or to provide helpers than are common.
Concerning ECC, we can even decide to drop software ECC for spinand.
Current spinand device embed the required ecc hardware, correctly
designed for the target nand (required ecc strength).
(may be I'm wrong on this point)
Arnaud
>
> Thanks
>
> Qi Wang
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2014-11-21 9:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.22397.1416508326.22890.linux-mtd@lists.infradead.org>
2014-11-21 1:16 ` [PATCH 0/2] staging: mtd: Support for GigaDevice SPI NAND flash Qi Wang 王起 (qiwang)
2014-11-21 9:24 ` arnaud.mouiche [this message]
2014-11-21 11:51 ` Ezequiel Garcia
2014-11-20 8:39 bpqw
2014-11-20 13:18 ` Ezequiel Garcia
2014-11-25 7:02 ` bpqw
2014-11-25 16:59 ` 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=546F04DF.4010501@gmail.com \
--to=arnaud.mouiche@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.