From: Andrea Scian <rnd4@dave-tech.it>
To: Richard Weinberger <richard@nod.at>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-kernel@vger.kernel.org, Han Xu <b45815@freescale.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [RFC PATCH 2/2] mtd: nand: use nand_check_erased_ecc_chunk in default ECC read functions
Date: Thu, 6 Aug 2015 06:28:45 +0200 [thread overview]
Message-ID: <55C2E27D.3030406@dave-tech.it> (raw)
In-Reply-To: <55C067F7.3000309@nod.at>
Il 04/08/2015 09:21, Richard Weinberger ha scritto:
> Andrea,
>
> Am 04.08.2015 um 09:02 schrieb Andrea Scian:
>>> I'm not sure whether introducing a read-before-write check is the best solution.
>>> At least we need hard numbers for slow/old SLC NANDs too.
>>
>> We can enable the feature only for MLC, AFAIK it has not been required for old SLC ;-)
>
> I think this needs more discussion.
>
> Boris, Brian, will you be at Embedded Linux Conference Europe in Dublin?
> Maybe we can discuss these issues (data retention, ff-checks, etc...) in person and
> figure out where to address them.
> I really want to avoid ad-hoc solutions. :)
Maybe I'll be at ELCE this year too
I'll be glad to meet all of you in person and participate to this
discussion. :)
It will be nice if also some silicon vendor would like to participate. I
know that someone from micron is actively following us on this ML, but I
don't really know if there's someone here in Europe. :)
>
>> Thanks.
>> In your opinion, enabling chk_io is correct to rough estimate the overhead
>> or does it enable too much checks?
>
> You mean the other checks bedside of self_check_write()? You can comment them out
> for your tests.
>
> Thanks,
> //richard
>
Kind Regards,
--
Andrea SCIAN
DAVE Embedded Systems
next prev parent reply other threads:[~2015-08-06 4:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 17:34 [RFC PATCH 0/2] mtd: nand: properly handle bitflips in erased pages Boris Brezillon
2015-07-30 17:34 ` [RFC PATCH 1/2] mtd: nand: add nand_check_erased helper functions Boris Brezillon
2015-07-31 7:10 ` Boris Brezillon
2015-07-31 10:06 ` Andrea Scian
2015-07-31 10:21 ` Boris Brezillon
2015-07-31 13:29 ` Andrea Scian
2015-07-31 13:58 ` Boris Brezillon
2015-08-04 15:42 ` Andrea Scian
2015-08-04 16:27 ` Boris Brezillon
2015-07-30 17:34 ` [RFC PATCH 2/2] mtd: nand: use nand_check_erased_ecc_chunk in default ECC read functions Boris Brezillon
2015-07-31 10:07 ` Andrea Scian
2015-07-31 10:32 ` Boris Brezillon
2015-07-31 13:40 ` Andrea Scian
2015-07-31 14:10 ` Boris Brezillon
2015-07-31 16:19 ` Andrea Scian
2015-07-31 16:27 ` Boris Brezillon
2015-08-03 11:16 ` Andrea Scian
2015-08-03 12:42 ` Boris Brezillon
2015-08-03 13:39 ` Andrea Scian
2015-08-03 19:32 ` Richard Weinberger
2015-08-04 7:02 ` Andrea Scian
2015-08-04 7:21 ` Richard Weinberger
2015-08-06 4:28 ` Andrea Scian [this message]
2015-08-06 9:19 ` Boris Brezillon
2015-08-06 9:42 ` Richard Weinberger
[not found] <mailman.4457.1438277726.1758.linux-mtd@lists.infradead.org>
[not found] <mailman.4514.1438332781.1758.linux-mtd@lists.infradead.org>
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=55C2E27D.3030406@dave-tech.it \
--to=rnd4@dave-tech.it \
--cc=b45815@freescale.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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
Powered by JetHome