From: Santhosh Kumar K <s-k6@ti.com>
To: <miquel.raynal@bootlin.com>, <richard@nod.at>, <vigneshr@ti.com>,
<tudor.ambarus@linaro.org>, <pratyush@kernel.org>,
<mwalle@kernel.org>, <tkuw584924@gmail.com>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<praneeth@ti.com>, <p-mantena@ti.com>, <a-dutta@ti.com>,
<u-kumar1@ti.com>, <s-k6@ti.com>
Subject: Re: [PATCH] mtd: spi-nor: spansion: Modify addr_mode_nbytes for DTR mode
Date: Mon, 15 Sep 2025 13:11:09 +0530 [thread overview]
Message-ID: <9fec8944-3bcd-4f89-b7d4-c5f5f9d6c185@ti.com> (raw)
In-Reply-To: <20250904131309.3095165-1-s-k6@ti.com>
Hello Pratyush and Takahiro,
On 04/09/25 18:43, Santhosh Kumar K wrote:
> The nor->params->addr_mode_nbytes parameter defines the address byte
> count for the current addressing mode. When transitioning between SDR
> and DDR modes, this parameter must be properly updated to maintain the
> correct addressing behavior. So, implement the necessary updates to
> nor->params->addr_mode_nbytes during both DDR mode enablement and
> disablement operations to ensure address byte counts remain consistent
> with the active transfer mode.
>
> Signed-off-by: Santhosh Kumar K <s-k6@ti.com>
> ---
>
> Tested on TI's AM62x SK
> Logs: https://gist.github.com/santhosh21/8d69756bd54605d79086b00850e1083a
We were facing write and erase failures in NOR flashes without this fix.
Failure log:
root@am62xx-evm:~# flash_erase /dev/mtd6 0 0
Erasing 256 Kibyte @ 0 -- 0 % complete [ 33.078034] spi-nor spi0.0:
Erase Error occurred
[ 33.086178] spi-nor spi0.0: Erase Error occurredock 0 (mtd6)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd6: MTD Erase entire chip failureTrying one
by one each sector.
error 5 (Input/output error)
Erasing 256 Kibyte @ 0 -- 0 % complete libmtd: error!: MEMERASE64 ioctl
failed for eraseblock 0 (mtd6)
error 5 (Input/output error)
flash_erase: error!: /dev/mtd6: MTD Erase failure
error 5 (Input/output error)
Erasing 256 Kibyte @ 0 -- 100 % complete
root@am62xx-evm:~#
But, I just bisected and got to know that the
commit b61c35e3404557779ec427c077f7a9f057bb053d
"mtd: spi-nor: spansion: Use nor->addr_nbytes in octal DTR mode in
RD_ANY_REG_OP"
fixed this issue. My bad!
Lets drop this patch.
Thanks and Regards,
Santhosh.
prev parent reply other threads:[~2025-09-15 7:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 13:13 Santhosh Kumar K
2025-09-04 13:35 ` Tudor Ambarus
2025-09-04 14:28 ` Pratyush Yadav
2025-09-08 9:28 ` Takahiro Kuwano
2025-09-15 7:41 ` Santhosh Kumar K [this message]
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=9fec8944-3bcd-4f89-b7d4-c5f5f9d6c185@ti.com \
--to=s-k6@ti.com \
--cc=a-dutta@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=p-mantena@ti.com \
--cc=praneeth@ti.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tkuw584924@gmail.com \
--cc=tudor.ambarus@linaro.org \
--cc=u-kumar1@ti.com \
--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®