From: Miquel Raynal <miquel.raynal@bootlin.com>
To: sashiko-bot@kernel.org
Cc: "Santhosh Kumar K" <s-k6@ti.com>,
sashiko-reviews@lists.linux.dev,
"Pratyush Yadav" <pratyush@kernel.org>,
devicetree@vger.kernel.org,
"Takahiro Kuwano" <takahiro.kuwano@infineon.com>,
conor+dt@kernel.org, "Vignesh Raghavendra" <vigneshr@ti.com>,
robh@kernel.org, "Richard Weinberger" <richard@nod.at>,
"Michael Walle" <mwalle@kernel.org>
Subject: Re: [PATCH v6 15/17] mtd: spinand: negotiate optimal controller operating point before dirmap creation
Date: Wed, 29 Jul 2026 10:45:39 +0200 [thread overview]
Message-ID: <87fr12mbf0.fsf@bootlin.com> (raw)
In-Reply-To: <20260723120247.8E1BD1F000E9@smtp.kernel.org> (sashiko-bot@kernel.org's message of "Thu, 23 Jul 2026 12:02:23 +0000")
Hi Santhosh,
On 23/07/2026 at 12:02:23 GMT, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 4 potential issue(s) to consider:
> - [High] Ranked controller optimization downgrades the read variant on tuning failure but fails to update or disable continuous read, leading to potential controller lockups and data corruption.
> - [High] The SPI NAND chip is unconditionally restored to ODTR mode upon system resume, even if controller optimization dynamically fell back to SSDR mode at probe time, breaking statically configured dirmaps.
> - [High] SPI controller PHY tuning state is lost across suspend/resume cycles.
> - [Medium] `spinand->max_write_op` is not reset between iterations in
> `spinand_try_ranked_variant()`, leaking `max_freq` modifications
> across tuning attempts.
The four reports seem legitimate. Some are easy to fix, the one about
continuous reads is a real concern I also had during my previous review
but forgot about it, and it is going to be slightly more challenging
than the others to handle properly. Of course we want both features to
work together, ideally.
Thanks,
Miquèl
next prev parent reply other threads:[~2026-07-29 8:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 11:02 [PATCH v6 00/17] spi: cadence-quadspi: add PHY tuning support Santhosh Kumar K
2026-07-23 11:02 ` [PATCH v6 01/17] spi: dt-bindings: add spi-max-post-config-frequency-hz property Santhosh Kumar K
2026-07-23 11:02 ` [PATCH v6 02/17] spi: dt-bindings: add spi-phy-pattern-partition property Santhosh Kumar K
2026-07-23 11:02 ` [PATCH v6 03/17] spi: parse spi-max-post-config-frequency-hz into post_config_max_speed_hz Santhosh Kumar K
2026-07-23 11:02 ` [PATCH v6 04/17] spi: spi-mem: teach spi_mem_adjust_op_freq() about post-config ops Santhosh Kumar K
2026-07-23 11:34 ` sashiko-bot
2026-07-29 8:40 ` Miquel Raynal
2026-07-23 11:02 ` [PATCH v6 05/17] spi: spi-mem: add execute_tuning callback and spi_mem_execute_tuning() Santhosh Kumar K
2026-07-23 11:30 ` sashiko-bot
2026-07-29 8:37 ` Miquel Raynal
2026-07-23 11:02 ` [PATCH v6 06/17] spi: cadence-quadspi: move cqspi_readdata_capture earlier Santhosh Kumar K
2026-07-23 11:02 ` [PATCH v6 07/17] spi: cadence-quadspi: add DQS support to read data capture Santhosh Kumar K
2026-07-23 11:28 ` sashiko-bot
2026-07-23 11:02 ` [PATCH v6 08/17] spi: cadence-quadspi: add PHY tuning support Santhosh Kumar K
2026-07-23 11:33 ` sashiko-bot
2026-07-23 11:02 ` [PATCH v6 09/17] spi: cadence-quadspi: skip DDR PHY tuning for 2-byte-address ops (i2383) Santhosh Kumar K
2026-07-23 11:48 ` sashiko-bot
2026-07-23 11:02 ` [PATCH v6 10/17] spi: cadence-quadspi: refactor direct read path for PHY support Santhosh Kumar K
2026-07-23 11:41 ` sashiko-bot
2026-07-23 11:02 ` [PATCH v6 11/17] spi: cadence-quadspi: enable PHY for direct reads Santhosh Kumar K
2026-07-23 11:48 ` sashiko-bot
2026-07-23 11:02 ` [PATCH v6 12/17] spi: cadence-quadspi: enable PHY for indirect writes Santhosh Kumar K
2026-07-23 11:44 ` sashiko-bot
2026-07-23 11:02 ` [PATCH v6 13/17] spi: cadence-quadspi: reprogram CS timing on every chip-select switch Santhosh Kumar K
2026-07-23 11:49 ` sashiko-bot
2026-07-23 11:02 ` [PATCH v6 14/17] mtd: spinand: extract variant ranking logic into spinand_op_find_best_variant() Santhosh Kumar K
2026-07-23 11:02 ` [PATCH v6 15/17] mtd: spinand: negotiate optimal controller operating point before dirmap creation Santhosh Kumar K
2026-07-23 12:02 ` sashiko-bot
2026-07-29 8:45 ` Miquel Raynal [this message]
2026-07-23 11:02 ` [PATCH v6 16/17] mtd: spi-nor: extract read op template construction into helper Santhosh Kumar K
2026-07-23 11:02 ` [PATCH v6 17/17] mtd: spi-nor: run controller optimization before dirmap creation Santhosh Kumar K
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=87fr12mbf0.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=mwalle@kernel.org \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=s-k6@ti.com \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=takahiro.kuwano@infineon.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