From: Mark Brown <broonie@kernel.org>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Siddharth Vadapalli <s-vadapalli@ti.com>,
Anurag Dutta <a-dutta@ti.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] spi: cadence-quadspi: Fix clock enable underflows due to runtime PM
Date: Thu, 4 Dec 2025 13:28:01 +0000 [thread overview]
Message-ID: <555e9f6b-b8b6-4cc5-900b-63aaff8b4e6c@sirena.org.uk> (raw)
In-Reply-To: <aTFQv157O-wJjVrZ@gaggiata.pivistrello.it>
[-- Attachment #1: Type: text/plain, Size: 593 bytes --]
On Thu, Dec 04, 2025 at 10:13:35AM +0100, Francesco Dolcini wrote:
> Unless I did some stupid mistake testing the patch, it does not fix the issue.
> Here the log with v6.18 + this patch
Yeah, I'm pretty sure it didn't work. I've managed to find a system
which instantiates the IP so hopefully I can modify it to trigger the
issue and test directly rather than working blind, I've also noticed
that we're getting
[ 15.430306] cadence-qspi 13010000.spi: Runtime PM usage count underflow!
even in normal operation (on that system anyway) so the runtime PM
handling is definitely unhappy.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-12-04 13:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 22:53 Mark Brown
2025-12-03 10:42 ` Siddharth Vadapalli
2025-12-03 11:58 ` Mark Brown
2025-12-04 9:13 ` Francesco Dolcini
2025-12-04 13:28 ` Mark Brown [this message]
2025-12-04 13:44 ` Mark Brown
2025-12-04 14:05 ` Nishanth Menon
2025-12-04 15:11 ` Mark Brown
2025-12-04 17:05 ` Mark Brown
2025-12-05 12:54 ` Dutta, Anurag
2025-12-05 12:58 ` Dutta, Anurag
2025-12-05 13:25 ` Mark Brown
2025-12-09 5:43 ` Dutta, Anurag
2025-12-09 9:52 ` Dutta, Anurag
2025-12-09 10:30 ` Mark Brown
2025-12-12 4:34 ` Dutta, Anurag
2025-12-12 6:04 ` Mark Brown
2025-12-12 6:07 ` Mark Brown
2025-12-12 7:14 ` Dutta, Anurag
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=555e9f6b-b8b6-4cc5-900b-63aaff8b4e6c@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a-dutta@ti.com \
--cc=francesco@dolcini.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=s-vadapalli@ti.com \
--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
all inboxes | Powered by JetHome®