linux-kernel - Re: [PATCH v7 1/7] dt-bindings: arm: Add support for Qualcomm TGU trace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47c055ae-c3da-4a9a-8a09-b567b1a80628@oss.qualcomm.com>
Date: Thu, 6 Nov 2025 10:24:46 +0800
From: Songwei Chai <songwei.chai@....qualcomm.com>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: andersson@...nel.org, alexander.shishkin@...ux.intel.com,
        kernel@....qualcomm.com, mike.leach@...aro.org, suzuki.poulose@....com,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-arm-msm@...r.kernel.org, coresight@...ts.linaro.org,
        devicetree@...r.kernel.org
Subject: Re: [PATCH v7 1/7] dt-bindings: arm: Add support for Qualcomm TGU
 trace



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