From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <Tudor.Ambarus@microchip.com>,
<linux-mtd@lists.infradead.org>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
Adam Ford <aford173@gmail.com>,
ladis@triops.cz, Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH v3 0/9] Better solution for the OMAP fix
Date: Wed, 27 Jan 2021 21:30:11 +0100 [thread overview]
Message-ID: <20210127203020.9574-1-miquel.raynal@bootlin.com> (raw)
Hello,
I recently got a bug report regarding the OMAP driver. We fixed it and
merged the fix. This fix was involving accessing BCH internal values
from within the OMAP driver which is far from ideal.
Now that the urgence is gone, here is a series to do it "the proper
way".
Cheers,
Miquèl
Main changes in v3:
* Export the number of ECC steps
* Add a 'get number of ECC bytes per step' helper.
Miquel Raynal (9):
mtd: nand: Let ECC engines advertize the exact number of steps
mtd: nand: ecc-bch: Populate the public nsteps field
mtd: nand: ecc-hamming: Populate the public nsteps field
mtd: nand: Add a helper to retrieve the number of ECC steps
mtd: nand: Add a helper to retrieve the number of ECC bytes per step
mtd: rawnand: Try not to use the ECC private structures
mtd: rawnand: omap: Use ECC information from the generic structures
mtd: nand: ecc-bch: Use the public nsteps field
mtd: nand: ecc-hamming: Use the public nsteps field
drivers/mtd/nand/ecc-sw-bch.c | 10 +++++-----
drivers/mtd/nand/ecc-sw-hamming.c | 10 +++++-----
drivers/mtd/nand/raw/nand_base.c | 16 +++++++---------
drivers/mtd/nand/raw/omap2.c | 14 ++++++++------
include/linux/mtd/nand-ecc-sw-bch.h | 2 --
include/linux/mtd/nand-ecc-sw-hamming.h | 2 --
include/linux/mtd/nand.h | 22 ++++++++++++++++++++++
7 files changed, 47 insertions(+), 29 deletions(-)
--
2.20.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2021-01-27 20:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 20:30 Miquel Raynal [this message]
2021-01-27 20:30 ` [PATCH v3 1/9] mtd: nand: Let ECC engines advertize the exact number of steps Miquel Raynal
2021-02-06 12:59 ` Adam Ford
2021-03-02 16:33 ` Miquel Raynal
2021-01-27 20:30 ` [PATCH v3 2/9] mtd: nand: ecc-bch: Populate the public nsteps field Miquel Raynal
2021-03-02 16:33 ` Miquel Raynal
2021-01-27 20:30 ` [PATCH v3 3/9] mtd: nand: ecc-hamming: " Miquel Raynal
2021-03-02 16:33 ` Miquel Raynal
2021-01-27 20:30 ` [PATCH v3 4/9] mtd: nand: Add a helper to retrieve the number of ECC steps Miquel Raynal
2021-03-02 16:33 ` Miquel Raynal
2021-01-27 20:30 ` [PATCH v3 5/9] mtd: nand: Add a helper to retrieve the number of ECC bytes per step Miquel Raynal
2021-03-02 16:33 ` Miquel Raynal
2021-01-27 20:30 ` [PATCH v3 6/9] mtd: rawnand: Try not to use the ECC private structures Miquel Raynal
2021-03-02 16:33 ` Miquel Raynal
2021-01-27 20:30 ` [PATCH v3 7/9] mtd: rawnand: omap: Use ECC information from the generic structures Miquel Raynal
2021-03-02 16:33 ` Miquel Raynal
2021-01-27 20:30 ` [PATCH v3 8/9] mtd: nand: ecc-bch: Use the public nsteps field Miquel Raynal
2021-03-02 16:33 ` Miquel Raynal
2021-01-27 20:30 ` [PATCH v3 9/9] mtd: nand: ecc-hamming: " Miquel Raynal
2021-03-02 16:33 ` Miquel Raynal
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=20210127203020.9574-1-miquel.raynal@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=aford173@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=ladis@triops.cz \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.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 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.