linux-kernel - Re: [PATCH 1/4] arm64: dts: ti: k3-j721e-main: Make the "scm

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: <d8a8293d-2759-4408-b1a7-a2689383b043@ti.com>
Date: Tue, 1 Jul 2025 15:53:56 +0530
From: Jayesh Choudhary <j-choudhary@...com>
To: Krzysztof Kozlowski <krzk@...nel.org>, <nm@...com>, <vigneshr@...com>,
        <devicetree@...r.kernel.org>
CC: <kristo@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
        <conor+dt@...nel.org>, <s-vadapalli@...com>, <rogerq@...nel.org>,
        <afd@...com>, <linux-kernel@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/4] arm64: dts: ti: k3-j721e-main: Make the "scm_conf"
 node a "simple-bus"

Hello Krzysztof,

On 04/06/25 15:18, Jayesh Choudhary wrote:
> Hello Krzysztof,
> 
> On 03/06/25 16:32, Krzysztof Kozlowski wrote:
>> On 03/06/2025 11:56, Jayesh Choudhary wrote:
>>> The "scm_conf" bus need not be "syscon". Now that we have "pcie*_ctrl"
>>> child nodes for "ti,syscon-pcie-ctrl" property in "pcie" nodes, change
>>> "scm_conf" node to "simple-bus".
>>> Also remove "reg" property as it is not needed by "simple-bus".
>>
>> This (possibly) affects all other users of DTS which were expecting this
>> ABI. It's not only about forward-compatibility, but other projects.
>>
>> Maybe this doe snot matter for you, so explain that in commit msg and
>> provide rationale why you are affecting other users.
>>
>>
> 
> This should not affect other users of DTS. J784S4 already has this
> change and it serves as a validation that DT nodes are compatible
> with other projects (for example uboot driver handles it).
> Other SoCs are being modified with taking J784S4 as a working reference.
> 
> Considering this, do I still need to add something? Or is it okay
> since I am not exactly affecting other projects?
> Should I add something along the lines of "similar to j784s4...."?
> 

Gentle ping on the above comment.

I have checked other projects like Barebox. That supports TI K3 SoC
but only AM62x and AM62L. Nothing in this series affects it.

Warm Regards,
Jayesh


> 
>>
>> Best regards,
>> Krzysztof