From: Mark Brown <broonie@kernel.org>
To: Ron Economos <re@w6rz.net>
Cc: miquel.raynal@bootlin.com, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
wsa+renesas@sang-engineering.com
Subject: Re: spi: Regression with v7.0-rc1 on VisionFive 2
Date: Sat, 28 Feb 2026 14:06:17 +0000 [thread overview]
Message-ID: <aaL2WVO_7bl6vNp5@sirena.co.uk> (raw)
In-Reply-To: <a3ca5e9b-7446-497e-8df2-7ef2b42a02e9@w6rz.net>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Sat, Feb 28, 2026 at 05:54:06AM -0800, Ron Economos wrote:
> I'm getting an SPI failure with Linux v7.0-rc1 on the VisionFive 2 RISC-V board.
> Feb 28 00:29:33 visionfive kernel: cadence-qspi 13010000.spi: QSPI is still busy after 500ms timeout.
> Feb 28 00:29:33 visionfive kernel: cadence-qspi 13010000.spi: detected FIFO depth (1) different from config (256)
> Feb 28 00:29:33 visionfive kernel: cadence-qspi 13010000.spi: QSPI is still busy after 500ms timeout.
> Feb 28 00:29:33 visionfive kernel: cadence-qspi 13010000.spi: QSPI is still busy after 500ms timeout.
> Feb 28 00:29:33 visionfive kernel: spi-nor spi1.0: operation failed with -110
> Feb 28 00:29:33 visionfive kernel: spi-nor spi1.0: probe with driver spi-nor failed with error -110
FWIW confirmed on my system:
https://lava.sirena.org.uk/scheduler/job/2504026#L715
(which I didn't notice as that was just buildroot and not running
kselftest-dt...).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-02-28 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 13:54 spi: Regression with v7.0-rc1 on VisionFive 2 Ron Economos
2026-02-28 14:06 ` Mark Brown [this message]
2026-02-28 14:22 ` Conor Dooley
2026-02-28 15:39 ` Conor Dooley
2026-03-02 8:27 ` Miquel Raynal
2026-03-04 17:02 ` Miquel Raynal
2026-03-04 21:52 ` Ron Economos
2026-03-06 21:35 ` Mark Brown
2026-03-06 23:37 ` Ron Economos
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=aaL2WVO_7bl6vNp5@sirena.co.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=re@w6rz.net \
--cc=wsa+renesas@sang-engineering.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