Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jie Gan <jie.gan@oss.qualcomm.com>
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>,
	Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>,
	Jingyi Wang <jingyi.wang@oss.qualcomm.com>,
	Abel Vesa <abel.vesa@oss.qualcomm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Mike Leach <mike.leach@arm.com>,
	James Clark <james.clark@linaro.org>, Leo Yan <leo.yan@arm.com>,
	Yuanfang Zhang <yuanfang.zhang@oss.qualcomm.com>,
	Abel Vesa <abelvesa@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, coresight@lists.linaro.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/5] dt-bindings: arm: coresight-tnoc: Add standalone qcom,coresight-agtnoc compatible
Date: Wed, 1 Jul 2026 09:26:34 +0200	[thread overview]
Message-ID: <9aa63427-ba41-436d-ab19-a533082d336a@kernel.org> (raw)
In-Reply-To: <4117c406-0d75-4eb1-842e-1d346b7fbf99@oss.qualcomm.com>

On 01/07/2026 09:16, Jie Gan wrote:
> 
> 
> On 7/1/2026 2:57 PM, Krzysztof Kozlowski wrote:
>> On Wed, Jul 01, 2026 at 09:53:41AM +0800, Jie Gan wrote:
>>> The TNOC compatible previously only allowed the two-string AMBA form
>>> "qcom,coresight-tnoc", "arm,primecell", which forces the device onto the
>>> AMBA bus.
>>>
>>> Convert the compatible to a oneOf and add a standalone
>>> "qcom,coresight-agtnoc" compatible alongside the existing AMBA form. The
>>> standalone string carries no "arm,primecell" entry, so the device is
>>> created on the platform bus instead of the AMBA bus.
>>
>> That's a Linux driver specific reason, so not a valid one.
>>
>> Describe the hardware instead.
>>
>> Also, you do not get other compatible for the same device.
> 
> The device is intended to be discovered and probed via the AMBA bus. 
> However, due to a hardware issue, AMBA probing does not work correctly. 
> While adding the arm,primecell-periphid property would allow the 

If this is not AMBA bus device, then drop primecell compatible.

> existing AMBA driver to bind, but I think that's a temp WA. As 
> Suzuki/Leo pointed out, we should not add the property to pretend the 
> device as an AMBA device.
> 
> Instead, I introduced a dedicated compatible string so the device can be 
> handled by the existing platform driver without relying on the missing 

As I said, that's a Linux driver specific reason, so not a valid one.

Fix your drivers if you insist on that.

> AMBA primecell identification. The purpose of the new compatible is to 
> clearly distinguish this platform-specific case from the standard 
> AMBA-based implementation. Or shall I re-use the existing compatible 
> "qcom,coresight-tnoc" as platform standalone compatible?
> 
> We already have a similar pattern for the interconnect TraceNoC device, 
> which uses the platform-specific compatible string qcom,coresight-itnoc.
I do not see there a fake, duplicated compatible for the same device.
Can you elaborate how is that relevant?

Best regards,
Krzysztof

  reply	other threads:[~2026-07-01  7:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01  1:53 [PATCH v4 0/5] Fix traceNoC probe issue on multiple QCOM platforms Jie Gan
2026-07-01  1:53 ` [PATCH v4 1/5] dt-bindings: arm: coresight-tnoc: Add standalone qcom,coresight-agtnoc compatible Jie Gan
2026-07-01  6:57   ` Krzysztof Kozlowski
2026-07-01  7:16     ` Jie Gan
2026-07-01  7:26       ` Krzysztof Kozlowski [this message]
2026-07-01  7:31         ` Jie Gan
2026-07-01 11:02           ` Konrad Dybcio
2026-07-01 12:54             ` Jie Gan
2026-07-01 13:09               ` Konrad Dybcio
2026-07-01 13:30                 ` Krzysztof Kozlowski
2026-07-02  0:51                   ` Jie Gan
2026-07-01  1:53 ` [PATCH v4 2/5] coresight: tnoc: add AG tnoc standalone compatible to the platform driver Jie Gan
2026-07-01  2:08   ` sashiko-bot
2026-07-01  6:58   ` Krzysztof Kozlowski
2026-07-01  1:53 ` [PATCH v4 3/5] arm64: dts: qcom: kaanapali: fix traceNoC probe issue Jie Gan
2026-07-01  2:07   ` sashiko-bot
2026-07-01  1:53 ` [PATCH v4 4/5] arm64: dts: qcom: sm8750: " Jie Gan
2026-07-01  2:06   ` sashiko-bot
2026-07-01  1:53 ` [PATCH v4 5/5] arm64: dts: qcom: glymur: use Aggregator TNOC compatible 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=9aa63427-ba41-436d-ab19-a533082d336a@kernel.org \
    --to=krzk@kernel.org \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=abelvesa@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=coresight@lists.linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=james.clark@linaro.org \
    --cc=jie.gan@oss.qualcomm.com \
    --cc=jingyi.wang@oss.qualcomm.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=leo.yan@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.leach@arm.com \
    --cc=robh@kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=tingwei.zhang@oss.qualcomm.com \
    --cc=yuanfang.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