From: "Dutta, Anurag" <a-dutta@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Nishanth Menon <nm@ti.com>,
Francesco Dolcini <francesco@dolcini.it>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
<linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>,
"Gujulan Elango, Hari Prasath" <gehariprasath@ti.com>,
"Kumar, Udit" <u-kumar1@ti.com>
Subject: Re: [PATCH] spi: cadence-quadspi: Fix clock enable underflows due to runtime PM
Date: Fri, 12 Dec 2025 12:44:24 +0530 [thread overview]
Message-ID: <367c82bd-7121-402f-b459-d48feccc887b@ti.com> (raw)
In-Reply-To: <aTuxGAn_XvIK-mJG@sirena.co.uk>
On 12-12-2025 11:37, Mark Brown wrote:
> On Fri, Dec 12, 2025 at 10:04:47AM +0530, Dutta, Anurag wrote:
>
>>> Let me send a patch with pm_runtime_get_sync(). If changes are required,
>>> please let me know.
> BTW note that we do need to have a clock disable for the case where
> CQSPI_DISABLE_RUNTIME_PM is quirked in as well as the with/without
> runtime PM cases.
ok, will remove this :
if (!(ddata && (ddata->quirks & CQSPI_DISABLE_RUNTIME_PM)))
because pm_runtime_get_sync() >=0 will be true even if
pm_runtime_enable() is never invoked.
prev parent reply other threads:[~2025-12-12 7:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 22:53 [PATCH] spi: cadence-quadspi: Fix clock enable underflows due to runtime PM 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
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 [this message]
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=367c82bd-7121-402f-b459-d48feccc887b@ti.com \
--to=a-dutta@ti.com \
--cc=broonie@kernel.org \
--cc=francesco@dolcini.it \
--cc=gehariprasath@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nm@ti.com \
--cc=s-vadapalli@ti.com \
--cc=stable@vger.kernel.org \
--cc=u-kumar1@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