[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87plckit7j.fsf@bootlin.com>
Date: Sun, 24 Aug 2025 18:24:00 +0200
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Mikhail Kshevetskiy <mikhail.kshevetskiy@...sys.eu>
Cc: Richard Weinberger <richard@....at>, Vignesh Raghavendra
<vigneshr@...com>, Lorenzo Bianconi <lorenzo@...nel.org>, Ray Liu
<ray.liu@...oha.com>, Mark Brown <broonie@...nel.org>, Tudor Ambarus
<tudor.ambarus@...aro.org>, Martin Kurbanov
<mmkurbanov@...utedevices.com>, Takahiro Kuwano
<Takahiro.Kuwano@...ineon.com>, Cheng Ming Lin
<chengminglin@...c.com.tw>, linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-spi@...r.kernel.org
Subject: Re: [PATCH RESEND v2 3/4] mtd: spinand: repeat reading in regular
mode if continuous reading fails
Hello,
> + if (controller_is_buggy) {
> + /*
> + * Some spi controllers may not support reading up to
> + * erase block size. They will read less data than
> + * expected. If this happen disable continuous mode
> + * and repeat reading in normal mode.
> + */
> + spinand->cont_read_possible = false;
I am fine with the idea, but could we avoid this little dance and drop
the extra controller_is_buggy boolean, and just let
spinand_mtd_continuous_page_read() do the fixup and return -EAGAIN?
> + ret = spinand_mtd_regular_page_read(mtd, from, ops,
> + &max_bitflips);
> + }
> + } else {
> + ret = spinand_mtd_regular_page_read(mtd, from, ops,
> + &max_bitflips);
> + }
>
> if (ops->stats) {
> ops->stats->uncorrectable_errors +=
Thanks,
Miquèl
Powered by blists - more mailing lists