From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Tokunori Ikegami <ikegami.t@gmail.com>, miquel.raynal@bootlin.com
Cc: richard@nod.at, vigneshr@ti.com, linux-mtd@lists.infradead.org,
stable@vger.kernel.org
Subject: Re: [PATCH v7 0/4] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N
Date: Sun, 10 Apr 2022 10:51:17 +0200 [thread overview]
Message-ID: <6b09d10e-2098-9fb7-be4c-ae67d802cd2d@leemhuis.info> (raw)
In-Reply-To: <20220323170458.5608-1-ikegami.t@gmail.com>
Hi, this is your Linux kernel regression tracker. Top-posting for once,
to make this easily accessible to everyone.
Miquel, Richard, Vignesh: what's up here? This patchset fixes a
regression. It's quite old, so it's not that urgent, but it looked like
nothing happened for two and a half week now. Or was progress made
somewhere?
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I'm getting a lot of
reports on my table. I can only look briefly into most of them and lack
knowledge about most of the areas they concern. I thus unfortunately
will sometimes get things wrong or miss something important. I hope
that's not the case here; if you think it is, don't hesitate to tell me
in a public reply, it's in everyone's interest to set the public record
straight.
#regzbot poke
On 23.03.22 18:04, Tokunori Ikegami wrote:
> Since commit dfeae1073583("mtd: cfi_cmdset_0002: Change write buffer to
> check correct value") buffered writes fail on S29GL064N. This is
> because, on S29GL064N, reads return 0xFF at the end of DQ polling for
> write completion, where as, chip_good() check expects actual data
> written to the last location to be returned post DQ polling completion.
> Fix is to revert to using chip_good() for S29GL064N which only checks
> for DQ lines to settle down to determine write completion.
>
> Fixes: dfeae1073583("mtd: cfi_cmdset_0002: Change write buffer to check correct value")
> Signed-off-by: Tokunori Ikegami <ikegami.t@gmail.com>
> Cc: stable@vger.kernel.org
> Link: https://lore.kernel.org/r/b687c259-6413-26c9-d4c9-b3afa69ea124@pengutronix.de/
>
> Tokunori Ikegami (4):
> 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
> mtd: cfi_cmdset_0002: Rename chip_ready variables
>
> drivers/mtd/chips/cfi_cmdset_0002.c | 112 ++++++++++++++--------------
> include/linux/mtd/cfi.h | 1 +
> 2 files changed, 55 insertions(+), 58 deletions(-)
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-04-10 8:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 17:04 [PATCH v7 0/4] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N Tokunori Ikegami
2022-03-23 17:04 ` [PATCH v7 1/4] mtd: cfi_cmdset_0002: Move and rename chip_check/chip_ready/chip_good_for_write Tokunori Ikegami
2022-04-28 8:18 ` Miquel Raynal
2022-03-23 17:04 ` [PATCH v7 2/4] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N Tokunori Ikegami
2022-04-28 8:18 ` Miquel Raynal
2022-03-23 17:04 ` [PATCH v7 3/4] mtd: cfi_cmdset_0002: Add S29GL064N ID definition Tokunori Ikegami
2022-04-28 8:18 ` Miquel Raynal
2022-03-23 17:04 ` [PATCH v7 4/4] mtd: cfi_cmdset_0002: Rename chip_ready variables Tokunori Ikegami
2022-04-28 8:18 ` Miquel Raynal
2022-03-28 10:50 ` [PATCH v7 0/4] mtd: cfi_cmdset_0002: Use chip_ready() for write on S29GL064N Ahmad Fatoum
2022-03-28 15:31 ` Tokunori Ikegami
2022-04-10 8:51 ` Thorsten Leemhuis [this message]
2022-04-11 7:40 ` Miquel Raynal
2022-04-27 9:37 ` Miquel Raynal
2022-04-28 6:32 ` Vignesh Raghavendra
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=6b09d10e-2098-9fb7-be4c-ae67d802cd2d@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=ikegami.t@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).