mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: kaanapali: add coresight nodes
Date: Fri, 5 Dec 2025 21:18:59 +0800	[thread overview]
Message-ID: <b08bfb85-3aa2-4fa9-afd7-a27c3f5e8a1a@oss.qualcomm.com> (raw)
In-Reply-To: <93a4071c-d2dc-451f-bc4d-defeafe383ea@oss.qualcomm.com>



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@oss.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@1000f000 {
> 
> 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


  reply	other threads:[~2025-12-05 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05  8:36 Jie Gan
2025-12-05 11:20 ` Konrad Dybcio
2025-12-05 13:18   ` Jie Gan [this message]
2025-12-05 13:21     ` 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=b08bfb85-3aa2-4fa9-afd7-a27c3f5e8a1a@oss.qualcomm.com \
    --to=jie.gan@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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 \
    --cc=tingwei.zhang@oss.qualcomm.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

all inboxes | Powered by JetHome®