From: "Dutta, Anurag" <a-dutta@ti.com>
To: Mark Brown <broonie@kernel.org>,
Francesco Dolcini <francesco@dolcini.it>,
Siddharth Vadapalli <s-vadapalli@ti.com>
Cc: <linux-spi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v2] spi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing
Date: Tue, 16 Dec 2025 09:38:01 +0530 [thread overview]
Message-ID: <82ffe3bc-6789-43b5-a48c-a1f490a70c64@ti.com> (raw)
In-Reply-To: <176580718260.161463.4539075429059025833.b4-ty@kernel.org>
On 15-12-2025 19:29, Mark Brown wrote:
> On Thu, 04 Dec 2025 19:13:35 +0000, Mark Brown wrote:
>> The recent refactoring of where runtime PM is enabled done in commit
>> f1eb4e792bb1 ("spi: spi-cadence-quadspi: Enable pm runtime earlier to
>> avoid imbalance") made the fact that when we do a pm_runtime_disable()
>> in the error paths of probe() we can trigger a runtime disable which in
>> turn results in duplicate clock disables. This is particularly likely
>> to happen when there is missing or broken DT description for the flashes
>> attached to the controller.
>>
>> [...]
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
>
> Thanks!
>
> [1/1] spi: cadence-quadspi: Parse DT for flashes with the rest of the DT parsing
> commit: 9f0736a4e136a6eb61e0cf530ddc18ab6d816ba3
Hi Mark
I was under the impression that we are agreeing on this solution :
https://lore.kernel.org/all/20251212072312.2711806-1-a-dutta@ti.com/
Regards
Anurag
> All being well this means that it will be integrated into the linux-next
> tree (usually sometime in the next 24 hours) and sent to Linus during
> the next merge window (or sooner if it is a bug fix), however if
> problems are discovered then the patch may be dropped or reverted.
>
> You may get further e-mails resulting from automated or manual testing
> and review of the tree, please engage with people reporting problems and
> send followup patches addressing any issues that are reported if needed.
>
> If any updates are required or you are submitting further changes they
> should be sent as incremental updates against current git, existing
> patches will not be replaced.
>
> Please add any relevant lists and maintainers to the CCs when replying
> to this mail.
>
> Thanks,
> Mark
>
next prev parent reply other threads:[~2025-12-16 4:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 19:13 Mark Brown
2025-12-04 20:00 ` Nishanth Menon
2025-12-05 0:03 ` Mark Brown
2025-12-05 0:06 ` Mark Brown
2025-12-15 13:59 ` Mark Brown
2025-12-16 4:08 ` Dutta, Anurag [this message]
2025-12-16 14:34 ` Mark Brown
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=82ffe3bc-6789-43b5-a48c-a1f490a70c64@ti.com \
--to=a-dutta@ti.com \
--cc=broonie@kernel.org \
--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®