From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Boris Brezillon <boris.brezillon@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-mtd@lists.infradead.org,
"Bean Huo (beanhuo)" <beanhuo@micron.com>,
Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>
Subject: [PATCH 0/2] mtd: rawnand: micron: Fix on-die ECC
Date: Mon, 9 Jul 2018 23:09:35 +0200 [thread overview]
Message-ID: <20180709210937.30150-1-boris.brezillon@bootlin.com> (raw)
Chris, Bean,
Here are 2 patches for you to review/test. The first one is fixing
the layout definition, and unless I missed something it should be
correct.
The second one is just my understanding of how byte 5 of READ_ID works
based on our experience with the 4bit/512 on-die ECC chip we have
worked on and the other datasheet I had a look at.
I'm not 100% sure this will work for all chips, but might work for the
2 chips we support right now.
So please test and/or review it and let me know if this approach works.
Regards,
Boris
Boris Brezillon (2):
mtd: rawnand: micron: Define the proper layout for 8bit/512bytes
on-die ECC
mtd: rawnand: micron: Fix on-die ECC detection logic
drivers/mtd/nand/raw/nand_micron.c | 110 +++++++++++++++++++++++++------------
1 file changed, 75 insertions(+), 35 deletions(-)
--
2.14.1
next reply other threads:[~2018-07-09 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 21:09 Boris Brezillon [this message]
2018-07-09 21:09 ` [PATCH 1/2] mtd: rawnand: micron: Define the proper layout for 8bit/512bytes on-die ECC Boris Brezillon
2018-07-16 8:37 ` Chris Packham
2018-07-09 21:09 ` [PATCH 2/2] mtd: rawnand: micron: Fix on-die ECC detection logic Boris Brezillon
2018-07-16 8:36 ` Chris Packham
2018-07-10 8:10 ` [PATCH 0/2] mtd: rawnand: micron: Fix on-die ECC Boris Brezillon
2018-07-10 21:40 ` Chris Packham
2018-07-16 8:07 ` Chris Packham
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=20180709210937.30150-1-boris.brezillon@bootlin.com \
--to=boris.brezillon@bootlin.com \
--cc=beanhuo@micron.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--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