[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b08bfb85-3aa2-4fa9-afd7-a27c3f5e8a1a@oss.qualcomm.com>
Date: Fri, 5 Dec 2025 21:18:59 +0800
From: Jie Gan <jie.gan@....qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@....qualcomm.com>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>,
Tingwei Zhang <tingwei.zhang@....qualcomm.com>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: kaanapali: add coresight nodes
On 12/5/2025 7:20 PM, Konrad Dybcio wrote:
> On 12/5/25 9:36 AM, Jie Gan wrote:
>> Add CoreSight nodes to enable trace paths such as TPDM->ETF and STM->ETF.
>> These devices are part of the AOSS, CDSP, QDSS, modem and some small
>> subsystems, such as DCC, GCC, ipcc and so on.
>>
>> Signed-off-by: Jie Gan <jie.gan@....qualcomm.com>
>> ---
>> Dependency:
>> - gcc: https://lore.kernel.org/all/20251126-gcc_kaanapali-v3-v4-0-0fe73d6898e9@oss.qualcomm.com/
>> - ipcc: https://lore.kernel.org/all/20251031-knp-ipcc-v3-0-62ffb4168dff@oss.qualcomm.com/
>> - base dt: https://lore.kernel.org/all/20251204-knp-dts-v2-0-596d8398c6d3@oss.qualcomm.com/
>> ---
>
> [...]
>
>> + tpdm@...0f000 {
>
> This node is out of sorting order
>
Hi Konard,
Thanks for checking.
> Everything else checks out against the docs
>
>> ---
>> base-commit: b2c27842ba853508b0da00187a7508eb3a96c8f7
>> change-id: 20251205-add-coresight-nodes-for-kaanapali-27948a5ddffa
>> prerequisite-change-id: 20251204-knp-dts-4ad60e175645:v2
>> prerequisite-patch-id: 1057cce23a42b5be40a6266d510bc62f756e3578
>> prerequisite-patch-id: 9924e37fffbad0125759ee3aff03137bd1cacfc1
>> prerequisite-patch-id: f7455dd4049ba647ed5f13e14fb99844340ccacc
>> prerequisite-patch-id: efa90c4f38d2e85476f22cc0081d7fbb8a34973a
>> prerequisite-patch-id: 7fc8429ae2438ddf1aa0f0aa005293cc76540f22
>> prerequisite-change-id: 20251121-gcc_kaanapali-v3-ab91e1065bd4:v4
>> prerequisite-patch-id: 9a9cd779ee23419a023893f357decbe09da1e42f
>> prerequisite-patch-id: b7d46739fd97b16bbf635569018bdd809fd30966
>> prerequisite-patch-id: 0baee9ea7681fe6b4ab1c69f1e087427ad0050e9
>> prerequisite-patch-id: a7ee79adf85ce9c5aedca168a561a9560fa59b44
>> prerequisite-change-id: 20251028-knp-ipcc-6b4189f71121:v3
>> prerequisite-patch-id: 6cf08b941741eff023e37a6a8afd5478bdf0788d
>> prerequisite-patch-id: 0ad500fc45e104a874839181b5ae59a4867ba1cb
>> prerequisite-patch-id: 628073856ba29bc3ed64f801dda4c9c7d767f327
>
> This list however should deter you from sending.. it's impossible for the
> maintainers to resolve a list this long for you and there's a high chance
> there will be changes/rebases required because any subset of these patches
> you depend on may change during their reviews
>
Yes, that's the question. The good news is below two patch series
already got reviewed.
- gcc:
https://lore.kernel.org/all/20251126-gcc_kaanapali-v3-v4-0-0fe73d6898e9@oss.qualcomm.com/
- ipcc:
https://lore.kernel.org/all/20251031-knp-ipcc-v3-0-62ffb4168dff@oss.qualcomm.com/
Can I have your review-by tag after fix the order of the mentioned node?
Then I will send a new version with the tag after the dependency is
being cleaned.
Thanks,
Jie
> Konrad
Powered by blists - more mailing lists