linux-kernel - Re: [PATCH v2 0/2] Enable CTCU device for QCS8300

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <2e8366b3-c060-4bb8-9704-0a8f41901706@quicinc.com>
Date: Fri, 4 Jul 2025 16:07:41 +0800
From: Jie Gan <quic_jiegan@...cinc.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, Jie Gan <jie.gan@....qualcomm.com>,
        Suzuki K Poulose <suzuki.poulose@....com>,
        Mike Leach
	<mike.leach@...aro.org>,
        James Clark <james.clark@...aro.org>, Rob Herring
	<robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
	<conor+dt@...nel.org>,
        Bjorn Andersson <andersson@...nel.org>,
        Konrad Dybcio
	<konradybcio@...nel.org>
CC: <coresight@...ts.linaro.org>, <linux-arm-kernel@...ts.infradead.org>,
        <linux-arm-msm@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] Enable CTCU device for QCS8300



On 7/4/2025 3:54 PM, Krzysztof Kozlowski wrote:
> On 25/06/2025 02:59, Jie Gan wrote:
>>
>>
>> On 6/24/2025 5:59 PM, Jie Gan wrote:
>>> Enable CTCU device for QCS8300 platform. Add a fallback mechnasim in binding to utilize
>>> the compitable of the SA8775p platform becuase the CTCU for QCS8300 shares same
>>> configurations as SA8775p platform.
>>
>> Hi dear maintainers,
>>
>> I just realized it would be more efficient to introduce a common
>> compatible string for SoCs that include two TMC ETR devices.
>>
>> Most of these SoCs share the same CTCU data configuration, such as the
> 
> "Most" basically disqualifies your idea.

Okay, it's not a proper expression.
SoCs included two ETR devices shared same configuration. So I think use 
a common compatible for these SoCs is make sense for me and dont need to 
update the dt-binding again and again...

I will send a new patch to address this idea if it's acceptable.

> 
>> offsets for the ATID and IRQ registers, because they integrate the same
>> version of the CTCU hardware.
>>
>> So I propose introducing a common compatible string,
>> "coresight-ctcu-v2", to simplify the device tree configuration for these
>> platforms.
> 
> This is explained in writing bindings.

Yeah, explained in the code lines..

Thanks,
Jie

> 
> Best regards,
> Krzysztof