From: Johan Jonker <jbx6244@gmail.com>
To: miquel.raynal@bootlin.com
Cc: richard@nod.at, vigneshr@ti.com, heiko@sntech.de,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, yifeng.zhao@rock-chips.com
Subject: [PATCH v4 0/3] Fixes for Rockchip NAND controller driver
Date: Mon, 10 Jul 2023 14:40:55 +0200 [thread overview]
Message-ID: <08f694df-4c1d-f059-43fd-f1aee678062c@gmail.com> (raw)
This serie contains various fixes for the Rockchip NAND controller
driver that showed up while testing boot block writing.
Fixed are:
Always copy hwecc PA data to/from oob_poi buffer in order to be able
to read/write the various boot block layouts.
Add option to safely probe the driver on a NAND with unknown data layout.
Fix oobfree layout.
Changed V4:
Reduce subject size
Add 'Fixes:' tag
Reword
Changed V3:
Change patch order, layout fixes first
Change prefixes
Reword
State that patches break all existing jffs2 users
Changed V2:
Add tag
Add manufacturer ops
Reword
Johan Jonker (3):
mtd: rawnand: rockchip: fix oobfree offset and description
mtd: rawnand: rockchip: copy hwecc PA data to oob_poi buffer
mtd: rawnand: rockchip: add skipbbt option
.../mtd/nand/raw/rockchip-nand-controller.c | 52 ++++++++++++-------
1 file changed, 32 insertions(+), 20 deletions(-)
--
2.30.2
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2023-07-10 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 12:40 Johan Jonker [this message]
2023-07-10 12:42 ` [PATCH v4 1/3] mtd: rawnand: rockchip: fix oobfree offset and description Johan Jonker
2023-07-10 12:42 ` [PATCH v4 2/3] mtd: rawnand: rockchip: copy hwecc PA data to oob_poi buffer Johan Jonker
2023-07-12 12:43 ` Miquel Raynal
2023-07-10 12:42 ` [PATCH v4 3/3] mtd: rawnand: rockchip: add skipbbt option Johan Jonker
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=08f694df-4c1d-f059-43fd-f1aee678062c@gmail.com \
--to=jbx6244@gmail.com \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=yifeng.zhao@rock-chips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox