From: Jie Gan <jie.gan@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Abel Vesa <abelvesa@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jingyi Wang <jingyi.wang@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: qcom: kaanapali: Add CoreSight nodes for APSS debug block
Date: Mon, 19 Oct 2026 14:27:54 +0800 [thread overview]
Message-ID: <8a2f55ed-67cc-443b-bcfd-fba9c6f646e9@oss.qualcomm.com> (raw)
In-Reply-To: <1ee9b624-4580-4650-8e48-d517ce9eee3d@oss.qualcomm.com>
On 10/15/2026 5:06 PM, Konrad Dybcio wrote:
> On 10/15/26 4:26 AM, Jie Gan wrote:
>>
>>
>> On 10/14/2026 9:23 AM, Jie Gan wrote:
>>>
>>>
>>> On 10/13/2026 8:49 PM, Konrad Dybcio wrote:
>>>> On 9/22/26 12:35 PM, Jie Gan wrote:
>>>>> The APSS debug block is built with CoreSight devices like ETE,
>>>>> replicator, funnel and TMC ETF. Add dt nodes for these devices to enable
>>>>> ETM trace.
>
> [...]
>
>>>>> + tmc@1d029000 {
>>>>> + compatible = "arm,coresight-tmc", "arm,primecell";
>>>>> + reg = <0x0 0x1d029000 0x0 0x1000>;
>>>>> +
>>>>> + clocks = <&aoss_qmp>;
>>>>> + clock-names = "apb_pclk";
>>>>> + power-domains = <&cluster_pd>;
>>>>
>>>> Is there only being a single cluster_pd a mistake on kaanapali?
>>>>
>>>
>>> From psci map, KNP only has one cluster_pd shared among all CPUs.
>>>
>>> Hi Jingyi,
>>>
>>> Can you please help to comment this part?
>>
>> Hi Konrad,
>>
>> We have cross checked the cluster info.
>>
>> The PD configuration for these two clusters is identical byte-for-byte and is based on cluster_cl5. I believe this is why they share the same cluster PD.
>>
>> domain-idle-states {
>> cluster_cl5: cluster-sleep-0 {
>> compatible = "domain-idle-state";
>> arm,psci-suspend-param = <0x01000054>;
>> entry-latency-us = <2150>;
>> exit-latency-us = <1983>;
>> min-residency-us = <9144>;
>> };
>
> Right, the configuration is the same, but ganging them up in a single
> power-domain prevents one of the clusters from going offline
> independently from Linux's PoV
That's making sense, we need fix it.
Thanks,
Jie
>
> Konrad
next prev parent reply other threads:[~2026-10-19 6:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 10:35 [PATCH 0/4] Add ETM devices for multiple QCOM platforms Jie Gan
2026-09-22 10:35 ` [PATCH 1/4] arm64: dts: qcom: hamoa: Add CoreSight nodes for APSS debug block Jie Gan
2026-10-13 12:46 ` Konrad Dybcio
2026-10-14 1:13 ` Jie Gan
2026-09-22 10:35 ` [PATCH 2/4] arm64: dts: qcom: sm8750: " Jie Gan
2026-09-22 10:35 ` [PATCH 3/4] arm64: dts: qcom: kaanapali: " Jie Gan
2026-10-13 12:49 ` Konrad Dybcio
2026-10-14 1:23 ` Jie Gan
2026-10-15 2:26 ` Jie Gan
2026-10-15 9:06 ` Konrad Dybcio
2026-10-19 6:27 ` Jie Gan [this message]
2026-09-22 10:35 ` [PATCH 4/4] arm64: dts: qcom: glymur: " Jie Gan
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=8a2f55ed-67cc-443b-bcfd-fba9c6f646e9@oss.qualcomm.com \
--to=jie.gan@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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®