linux-kernel - Re: "complete" dt-bindings for new SoC

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4f0ec956-d796-4c62-995b-f8a879b444f0@kernel.org>
Date: Wed, 13 Aug 2025 07:48:55 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Chris Packham <Chris.Packham@...iedtelesis.co.nz>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>,
 "conor+dt@...nel.org" <conor+dt@...nel.org>,
 "robh+dt@...nel.org" <robh+dt@...nel.org>
Cc: "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: "complete" dt-bindings for new SoC

On 13/08/2025 06:56, Chris Packham wrote:
> Hi Devicetree Enthusiasts,
> 
> A few times now I've been told that things would have been easier had I 
> submitted a complete binding in the first place. I find myself looking 
> at another new SoC (a Realtek Switch with and integrated ARM64 core this 
> time). I'm also waiting on hardware so I figured I could probably get 
> the ball rolling on a devicetree and I wanted to do a better job of 
> writing the binding.
> 
> Which brings be to the question. What does a "complete" binding mean to 
> the devicetree maintainers? Are we talking about an overall binding for 
> the chip that calls out peripherals (some which already exist) with a 
> ref: ? Or a full binding in one document that covers everything in the 
> chip? Does it need to be accompanied by an actual dts(i) for the chip?


Writing bindings doc describes that. I would add on top - if SoC has
multiple devices of same class, like multiple clock controllers or
resets, this should be taken into account if not sending all of them.
And by taking account I mean think how complete picture will look like.
One SoC for RISV-V is example of that...

Best regards,
Krzysztof