From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Tokunori Ikegami <ikegami.t@gmail.com>
Cc: linux-mtd@lists.infradead.org,
Ahmad Fatoum <a.fatoum@pengutronix.de>,
stable@vger.kernel.org
Subject: Re: [PATCH v4 0/3] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N
Date: Wed, 16 Mar 2022 18:27:05 +0100 [thread overview]
Message-ID: <20220316182705.7b38828b@xps13> (raw)
In-Reply-To: <20220316155455.162362-1-ikegami.t@gmail.com>
Hi Tokunori,
ikegami.t@gmail.com wrote on Thu, 17 Mar 2022 00:54:52 +0900:
> As pointed out by this bug report [1], buffered writes are now broken on
> S29GL064N. This issue comes from a rework which switched from using chip_good()
> to chip_ready(), because DQ true data 0xFF is read on S29GL064N and an error
> returned by chip_good(). One way to solve the issue is to revert the change
> partially to use chip_ready for S29GL064N.
Thanks for your quick iterations but overall I seriously don't feel
this series is ready. At least right now I am still not satisfied by
its shape.
>
> [1] https://lore.kernel.org/r/b687c259-6413-26c9-d4c9-b3afa69ea124@pengutronix.de/
>
> Fixes: dfeae1073583("mtd: cfi_cmdset_0002: Change write buffer to check correct value")
... and this Fixes tag points to a v4.18 kernel, so if this is true, we
should have a backport-able patch. This also means that this is not as
critical than I thought if people already lived 4 years with the bug.
Vignesh, I let you continue iterating with Tokunori and ack the series
when you feel it's ready.
> Signed-off-by: Tokunori Ikegami <ikegami.t@gmail.com>
> Tested-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> Cc: stable@vger.kernel.org
>
> Tokunori Ikegami (3):
> mtd: cfi_cmdset_0002: Move and rename
> chip_check/chip_ready/chip_good_for_write
> mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N
> mtd: cfi_cmdset_0002: Add S29GL064N ID definition
>
> drivers/mtd/chips/cfi_cmdset_0002.c | 93 +++++++++++++++--------------
> 1 file changed, 49 insertions(+), 44 deletions(-)
>
Thanks,
Miquèl
prev parent reply other threads:[~2022-03-16 17:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 15:54 [PATCH v4 0/3] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N Tokunori Ikegami
2022-03-16 15:54 ` [PATCH v4 1/3] mtd: cfi_cmdset_0002: Move and rename chip_check/chip_ready/chip_good_for_write Tokunori Ikegami
2022-03-16 17:15 ` Miquel Raynal
2022-03-22 2:35 ` Tokunori Ikegami
2022-03-16 15:54 ` [PATCH v4 2/3] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N Tokunori Ikegami
2022-03-16 17:21 ` Miquel Raynal
2022-03-17 10:01 ` Vignesh Raghavendra
2022-03-17 14:16 ` Ahmad Fatoum
2022-03-22 2:49 ` Tokunori Ikegami
2022-03-28 10:49 ` Ahmad Fatoum
2022-03-28 15:27 ` Tokunori Ikegami
2022-03-22 2:42 ` Tokunori Ikegami
2022-03-22 2:39 ` Tokunori Ikegami
2022-03-21 11:48 ` Thorsten Leemhuis
2022-03-21 12:35 ` Miquel Raynal
2022-03-21 12:51 ` Thorsten Leemhuis
2022-03-21 13:41 ` Miquel Raynal
2022-03-21 14:17 ` Thorsten Leemhuis
2022-03-21 14:56 ` Miquel Raynal
2022-03-21 15:16 ` Thorsten Leemhuis
2022-03-22 2:51 ` Tokunori Ikegami
2022-03-16 17:27 ` Miquel Raynal [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=20220316182705.7b38828b@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=a.fatoum@pengutronix.de \
--cc=ikegami.t@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).