From: Songwei Chai <songwei.chai@oss.qualcomm.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: andersson@kernel.org, alexander.shishkin@linux.intel.com,
kernel@oss.qualcomm.com, mike.leach@linaro.org,
suzuki.poulose@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, coresight@lists.linaro.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v7 1/7] dt-bindings: arm: Add support for Qualcomm TGU trace
Date: Thu, 6 Nov 2025 10:24:46 +0800 [thread overview]
Message-ID: <47c055ae-c3da-4a9a-8a09-b567b1a80628@oss.qualcomm.com> (raw)
In-Reply-To: <17c3ee70-66e3-418f-8c79-926c8a139d16@kernel.org>
On 11/5/2025 5:06 PM, Krzysztof Kozlowski wrote:
> On 05/11/2025 09:49, Songwei Chai wrote:
>
>> Once again, I apologize for not including these modifications in the
>> changelog.
>>
>>> All qcom coresight bindings are called coresight and I do not see reason
>>> why this is being changed.
>>
>> The reason for removing the |coresight| keywords is that this patch
>> series was not
>>
>> accepted by the maintainers of the Coresight subsystem (as explained in
>> the cover letter).
>>
>> Therefore, we decided to make it a Qualcomm-specific driver.
>
> Use standard email paragraphs
>
> not
>
> broken
>
> by
>
> two lines each.
>
> Anyway, above discussion explains nothing about compatible. I might be
> missing something, so please quote here Mike the part where he asks to
> *change the compatible and hardware name*. Please quote EXACTLY that part.
"this component is primarily a part of the qualcom proprietary QPMDA
subsystem, and is capable of operating independently from the
CoreSight hardware trace generation system." -- From Mike
While he didn't explicitly ask to "change the compatible and hardware
name", from his above remark, i think he doesn't consider this component
to be part of the coresight subsystem as it can operate independently.
That's why, in the latest version of the binding, i've removed the
coresight keyword from the compatible.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-11-06 2:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 6:40 [PATCH v7 0/7] Provides support for Trigger Generation Unit Songwei Chai
2025-11-04 6:40 ` [PATCH v7 1/7] dt-bindings: arm: Add support for Qualcomm TGU trace Songwei Chai
2025-11-04 7:26 ` Rob Herring (Arm)
2025-11-05 7:49 ` Krzysztof Kozlowski
[not found] ` <746b292f-fc3a-43a8-89b1-76f61ccc0630@oss.qualcomm.com>
2025-11-05 8:15 ` Krzysztof Kozlowski
[not found] ` <b9e7f8ba-a629-4316-a6dd-d765ed0037ee@oss.qualcomm.com>
2025-11-05 9:03 ` Krzysztof Kozlowski
2025-11-05 10:16 ` Songwei Chai
2025-11-05 9:06 ` Krzysztof Kozlowski
2025-11-06 2:24 ` Songwei Chai [this message]
2025-11-04 6:40 ` [PATCH v7 2/7] qcom-tgu: Add TGU driver Songwei Chai
2025-11-04 6:40 ` [PATCH v7 3/7] qcom-tgu: Add signal priority support Songwei Chai
2025-11-04 6:40 ` [PATCH v7 4/7] qcom-tgu: Add TGU decode support Songwei Chai
2025-11-04 6:40 ` [PATCH v7 5/7] qcom-tgu: Add support to configure next action Songwei Chai
2025-11-04 6:40 ` [PATCH v7 6/7] qcom-tgu: Add timer/counter functionality for TGU Songwei Chai
2025-11-04 6:40 ` [PATCH v7 7/7] qcom-tgu: Add reset node to initialize Songwei Chai
2025-11-25 10:18 ` [PATCH v7 0/7] Provides support for Trigger Generation Unit Songwei Chai
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=47c055ae-c3da-4a9a-8a09-b567b1a80628@oss.qualcomm.com \
--to=songwei.chai@oss.qualcomm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andersson@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@oss.qualcomm.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.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