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: Re: [PATCH v2 1/2] mtd: spi-nor: sst: Fix write enable before AAI sequence
Date: Mon, 23 Feb 2026 09:17:33 +0000 [thread overview]
Message-ID: <20260223091733.47-1-sanjaikumarvs@gmail.com> (raw)
In-Reply-To: <DGM6ZPOT1WCR.157JI0LW4W3E8@kernel.org>
Hi Michael,
Thank you for the review.
> Raises concern about writes ending at odd offsets potentially having the same issue
The odd end address case (trailing byte) is already handled in the existing code at lines 243-255:
/* Write out trailing byte if it exists. */
if (actual != len) {
ret = spi_nor_write_enable(nor);
...
ret = sst_nor_write_data(nor, to, 1, buf + actual);
}
So write_enable is already called before writing the trailing byte. My patch only addresses the odd start case where BP clears WEL before the AAI sequence begins.
> Suggests simplifying the conditional logic by removing the length check
The condition `if (actual < len - 1)` avoids an unnecessary write_enable when len == 1 (single byte write at odd address, no AAI follows). But if you prefer unconditional write_enable for simplicity, I can change it in v3.
> Notes the patch lacks runtime testing
I don't have the hardware setup to test odd-address writes at the moment. The fix is based on code analysis. I have tested patch 2/2 (dirmap fallback) on hardware.
Please let me know if you'd like me to send a v3 with the simplified unconditional write_enable.
Thanks,
Sanjaikumar
next prev parent reply other threads:[~2026-02-23 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 9:42 [PATCH v2 0/2] mtd: spi-nor: Fix SST AAI write mode Sanjaikumar V S
2026-02-20 9:42 ` [PATCH v2 1/2] mtd: spi-nor: sst: Fix write enable before AAI sequence Sanjaikumar V S
2026-02-23 8:18 ` Michael Walle
2026-02-23 9:17 ` Sanjaikumar V S [this message]
2026-02-23 9:29 ` Michael Walle
2026-03-06 22:36 ` Hendrik Donner
2026-03-13 11:46 ` Pratyush Yadav
2026-03-13 12:50 ` Hendrik Donner
2026-03-13 13:39 ` Pratyush Yadav
2026-02-20 9:42 ` [PATCH v2 2/2] mtd: spi-nor: core: Fix AAI mode when dirmap is not available Sanjaikumar V S
2026-02-23 10:17 ` [PATCH v3 0/2] mtd: spi-nor: Fix SST AAI write mode Sanjaikumar V S
2026-02-23 10:17 ` [PATCH v3 1/2] mtd: spi-nor: sst: Fix write enable before AAI sequence Sanjaikumar V S
2026-02-23 10:17 ` [PATCH v3 2/2] mtd: spi-nor: core: Fix AAI mode when dirmap is not available Sanjaikumar V S
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=20260223091733.47-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