From: Sanjaikumar V S <sanjaikumarvs@gmail.com>
To: mwalle@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
miquel.raynal@bootlin.com, pratyush@kernel.org, richard@nod.at,
sanjaikumar.vs@dicortech.com, sanjaikumarvs@gmail.com,
stable@vger.kernel.org, tudor.ambarus@linaro.org,
vigneshr@ti.com
Subject: [PATCH v4 0/2] mtd: spi-nor: Fix SST AAI write mode
Date: Wed, 11 Mar 2026 10:30:55 +0000 [thread overview]
Message-ID: <20260311103057.29-1-sanjaikumarvs@gmail.com> (raw)
From: Sanjaikumar V S <sanjaikumar.vs@dicortech.com>
This patch series addresses two distinct problems affecting SST flash
Auto Address Increment write functionality:
1. When writes begin at odd addresses, a single byte is programmed first
using byte program command, which clears the Write Enable Latch. The
driver fails to re-enable writes before the AAI sequence.
2. When the SPI controller lacks direct mapping support, the fallback
path uses a probe-time operation template with standard page program
opcodes instead of AAI opcodes.
Changes in v4:
- Resent as new thread (v3 was incorrectly sent as reply to v2)
- Patch 2/2: Added Fixes tag
Changes in v3:
- Patch 1/2: Use local boolean 'needs_write_enable' for clarity as
suggested by Michael Walle
- Patch 1/2: Improved comment explaining the fix
- Patch 1/2: Added Fixes tag
Changes in v2:
- Split fixes into separate patches
- Added detailed commit messages
Sanjaikumar V S (2):
mtd: spi-nor: sst: Fix write enable before AAI sequence
mtd: spi-nor: core: Fix AAI mode when dirmap is not available
drivers/mtd/spi-nor/core.c | 2 +-
drivers/mtd/spi-nor/sst.c | 13 +++++++++++++
2 files changed, 14 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2026-03-11 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 10:30 Sanjaikumar V S [this message]
2026-03-11 10:30 ` [PATCH v4 1/2] mtd: spi-nor: sst: Fix write enable before AAI sequence Sanjaikumar V S
2026-03-16 13:44 ` Hendrik Donner
2026-03-11 10:30 ` [PATCH v4 2/2] mtd: spi-nor: core: Fix AAI mode when dirmap is not available Sanjaikumar V S
2026-03-16 13:44 ` Hendrik Donner
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=20260311103057.29-1-sanjaikumarvs@gmail.com \
--to=sanjaikumarvs@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=sanjaikumar.vs@dicortech.com \
--cc=stable@vger.kernel.org \
--cc=tudor.ambarus@linaro.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