Devicetree
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Sneh Mankad <sneh.mankad@oss.qualcomm.com>,
	Stephan Gerhold <stephan.gerhold@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thomas Gleixner <tglx@kernel.org>,
	Shawn Guo <shawn.guo@linaro.org>, Marc Zyngier <maz@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] irqchip/irq-qcom-mpm: Register MPM under CPU cluster power domain
Date: Wed, 19 Aug 2026 15:49:51 +0200	[thread overview]
Message-ID: <62f630d1-80d5-42d9-a818-945f3c67df2b@oss.qualcomm.com> (raw)
In-Reply-To: <d7402165-e4aa-4860-a1d3-92841df7e7c5@oss.qualcomm.com>

On 8/3/26 12:58 PM, Sneh Mankad wrote:
> 
> 
> On 15-Jul-26 4:04 PM, Stephan Gerhold wrote:
>> On Wed, Jul 15, 2026 at 11:46:58AM +0200, Konrad Dybcio wrote:
>>> On 7/13/26 12:25 PM, Sneh Mankad wrote:

[...]

>> I don't think this fallback is relevant for the non-PSCI QC platforms,
>> for the following reasons:
>>
>>  - They don't define the MPM.
>>  - They don't support cluster idle upstream, so they don't need to
>>    define the MPM. They can't reach the idle state where it would become
>>    relevant.
>>  - The setup for cluster idle without PSCI is essentially equivalent to
>>    OSI, except that the SPM/SAW driver needs to program the idle state
>>    to enter. There is one SPM/SAW for every idle domain (e.g. on
>>    MSM8939: 2x4 CPU, 2x Cluster, 1x System). You can just model the
>>    SPM/SAW instances as power domains to get the same setup as PSCI OSI
>>    (I had a draft for this at some point). So if someone ever implements
>>    this, we should be able to use the same approach as for PSCI OSI.
>>
>> I'm not aware of non-OSI PSCI platforms with MPM either, so I'm not sure
>> when this fallback would be used.
>>
>> We probably do need some fallback for the old sm6375/agatii DTBs though.
> 
> Yes Stephan, this fallback will be required for RPM targets that do not have
> power-domains property mentioned to facilitate the RPM notification in cluster
> idle states, including agatti and sm6375.

Will it be able to do anything useful though? Because if it were, we
might as well not change the bindings. Now don't get me wrong, I'm in
favor of straightening them out, but this sounds a bit unclear

Because if we lose nothing, we may simply not carry the fallback (i.e.
provide the interrupt part of mpm without the cluster notif)

Konrad

  reply	other threads:[~2026-08-19 13:49 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13 10:25 [PATCH 0/7] Register MPM under CPU cluster power domain to manage RPM notification Sneh Mankad
2026-07-13 10:25 ` [PATCH 1/7] dt-bindings: interrupt-controller: mpm: Document power-domains property Sneh Mankad
2026-07-13 10:36   ` sashiko-bot
2026-07-13 11:26   ` Konrad Dybcio
2026-08-03  5:28     ` Sneh Mankad
2026-07-13 15:11   ` Marc Zyngier
2026-07-15  6:38     ` Marek Szyprowski
2026-07-15  8:54       ` Marc Zyngier
2026-08-03 10:28         ` Sneh Mankad
2026-08-03 19:21           ` Dmitry Baryshkov
2026-07-21  9:06   ` Krzysztof Kozlowski
2026-08-03  5:30     ` Sneh Mankad
2026-08-03 19:21       ` Dmitry Baryshkov
2026-07-13 10:25 ` [PATCH 2/7] irqchip/irq-qcom-mpm: Register MPM under CPU cluster power domain Sneh Mankad
2026-07-13 10:41   ` sashiko-bot
2026-07-15  9:46   ` Konrad Dybcio
2026-07-15 10:34     ` Stephan Gerhold
2026-07-15 10:45       ` Konrad Dybcio
2026-07-15 10:49         ` Stephan Gerhold
2026-07-15 11:11           ` Konrad Dybcio
2026-07-21 22:18         ` Dmitry Baryshkov
2026-07-22  8:29           ` Konrad Dybcio
2026-08-03 10:58       ` Sneh Mankad
2026-08-19 13:49         ` Konrad Dybcio [this message]
2026-07-13 10:25 ` [PATCH 3/7] irqchip/irq-qcom-mpm: Prepare common access path for timer and pin regs Sneh Mankad
2026-07-13 10:39   ` sashiko-bot
2026-07-15  9:59   ` Konrad Dybcio
2026-07-13 10:25 ` [PATCH 4/7] irqchip/irq-qcom-mpm: Program wakeup timer when CPU cluster goes to LPM Sneh Mankad
2026-07-13 10:38   ` sashiko-bot
2026-07-13 15:18   ` Marc Zyngier
2026-08-03 11:03     ` Sneh Mankad
2026-07-13 10:25 ` [PATCH 5/7] arm64: dts: qcom: sm6375: Make MPM device as part of CPU cluster domain Sneh Mankad
2026-07-13 10:40   ` sashiko-bot
2026-07-13 10:25 ` [PATCH 6/7] arm64: dts: qcom: agatti: Do not mark MPM as power domain Sneh Mankad
2026-07-13 10:39   ` sashiko-bot
2026-07-15 10:01   ` Konrad Dybcio
2026-07-21 22:22     ` Dmitry Baryshkov
2026-07-22  8:28       ` Konrad Dybcio
2026-07-22 12:40         ` Dmitry Baryshkov
2026-08-03 10:37           ` Sneh Mankad
2026-07-21 22:21   ` Dmitry Baryshkov
2026-07-13 10:25 ` [PATCH 7/7] arm64: dts: qcom: shikra: Add CPU idle states Sneh Mankad
2026-07-15 10:02   ` Konrad Dybcio
2026-08-03 10:33     ` Sneh Mankad
2026-08-19 13:46       ` Konrad Dybcio

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=62f630d1-80d5-42d9-a818-945f3c67df2b@oss.qualcomm.com \
    --to=konrad.dybcio@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=sneh.mankad@oss.qualcomm.com \
    --cc=stephan.gerhold@linaro.org \
    --cc=tglx@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