linux-kernel - Re: [PATCH v3 6/8] arm64: dts: bst: add support for Black Sesame Technologies C1200 CDCU1.0 board

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

Message-ID: <179f19c0-d9fc-4efb-bc78-8dc1e7505b13@kernel.org>
Date: Fri, 5 Sep 2025 09:23:48 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Albert Yang <yangzh0906@...ndersoft.com>
Cc: adrian.hunter@...el.com, arnd@...db.de, conor+dt@...nel.org,
 devicetree@...r.kernel.org, gordon.ge@....ai, krzk+dt@...nel.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 robh@...nel.org
Subject: Re: [PATCH v3 6/8] arm64: dts: bst: add support for Black Sesame
 Technologies C1200 CDCU1.0 board

On 03/09/2025 09:06, Albert Yang wrote:
>>
>> No, you need to finally read and follow DTS coding style.
>>
>>>             gic: interrupt-controller@...00000 {
>>>                     compatible = "arm,gic-v3";
>>>
> 
> Thank you for pointing out the DTS coding style requirements. I have now
> carefully reviewed the documentation and updated the GIC node as follows.
> 
> I have a question regarding the property ordering. According to the DTS
> coding style documentation at:
> https://docs.kernel.org/devicetree/bindings/dts-coding-style.html
> 
> The preferred order of properties in device nodes is:
> 
> 1.“compatible”
> 2.“reg”
> 3.“ranges”
> 4.Standard/common properties (defined by common bindings, e.g. without vendor-prefixes)
> 5.Vendor-specific properties
> 6.“status” (if applicable)
> 7.Child nodes, where each node is preceded with a blank line
> 
> However, I'm uncertain about how to order properties that start with "#".
> I have treated them as standard/common properties and updated the node as follows.
> Could you please confirm if this approach is correct?

They go as standard common properties. Whether you group all '#'
together or sort by name skipping '#' is up to you, because common style
does not define that.

> 
> 
> 		gic: interrupt-controller@...00000 {
> 			compatible = "arm,gic-v3";
> 			reg = <0x0 0x32800000 0x0 0x10000>,
> 			      <0x0 0x32880000 0x0 0x100000>;
> 			ranges;
> 			#address-cells = <2>;
> 			#interrupt-cells = <3>;
> 			interrupt-controller;
> 			interrupts = <GIC_PPI 9 IRQ_TYPE_LEVEL_LOW>;
> 			#size-cells = <2>;

I would keep #size-cells after #address-cells, because they describe
same thing - addressing of children.



Best regards,
Krzysztof