mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James Hilliard <james.hilliard1@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>,
	 Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>
Cc: Maxim Levitsky <maximlevitsky@gmail.com>,
	 Boris Brezillon <bbrezillon@kernel.org>,
	 Brian Norris <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org,  linux-kernel@vger.kernel.org,
	James Hilliard <james.hilliard1@gmail.com>,
	 stable@vger.kernel.org
Subject: [PATCH 0/4] mtd: rawnand: restore SmartMedia setup in r852
Date: Sun, 08 Nov 2026 18:29:19 -0700	[thread overview]
Message-ID: <20261108-submit-r852-smartmedia-attach-v1-v1-0-56d08c0571a2@gmail.com> (raw)

r852 installs its own NAND controller, but the shared SmartMedia setup is
still attached to the unused legacy dummy controller. Run that setup from
r852's attach_chip callback so the media-specific OOB layout, bad-block
handling and page-size checks take effect. Restore the hardware-ECC
default during probe so the PCI path selects a valid engine without a
NAND device-tree node.

Before restoring the shared setup, correct the first ECC region's offset,
remove recursive NAND locking from the bad-block marking path, and select
the standard OOB writer for r852's contiguous spare area. These keep ECC
bytes away from the metadata and bad-block writes within the spare area.

Assisted-by: Codex:gpt-6-astra
Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

---
James Hilliard (4):
      mtd: rawnand: sm_common: restore the first ECC region offset
      mtd: rawnand: sm_common: avoid recursive locking when marking bad blocks
      mtd: rawnand: r852: use the standard OOB write operation
      mtd: rawnand: r852: restore SmartMedia and ECC initialization

 drivers/mtd/nand/raw/r852.c      |  9 +++++++
 drivers/mtd/nand/raw/sm_common.c | 55 ++++++++++++++++++++++------------------
 drivers/mtd/nand/raw/sm_common.h |  3 +++
 3 files changed, 42 insertions(+), 25 deletions(-)
---
base-commit: 30daaf3e7897b4a8d9b72e5b0c86dd6e2a4d7d85
change-id: 20261108-submit-r852-smartmedia-attach-v1-290991aae0aa

Best regards,
--  
James Hilliard <james.hilliard1@gmail.com>


             reply	other threads:[~2026-11-09  1:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09  1:29 James Hilliard [this message]
2026-11-09  1:29 ` [PATCH 1/4] mtd: rawnand: sm_common: restore the first ECC region offset James Hilliard
2026-11-09  1:29 ` [PATCH 2/4] mtd: rawnand: sm_common: avoid recursive locking when marking bad blocks James Hilliard
2026-11-09  1:29 ` [PATCH 3/4] mtd: rawnand: r852: use the standard OOB write operation James Hilliard
2026-11-09  1:29 ` [PATCH 4/4] mtd: rawnand: r852: restore SmartMedia and ECC initialization James Hilliard

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=20261108-submit-r852-smartmedia-attach-v1-v1-0-56d08c0571a2@gmail.com \
    --to=james.hilliard1@gmail.com \
    --cc=bbrezillon@kernel.org \
    --cc=computersforpeace@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=maximlevitsky@gmail.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®