From: Krzysztof Kozlowski <krzk@kernel.org>
To: Albert Yang <yangzh0906@thundersoft.com>
Cc: adrian.hunter@intel.com, arnd@arndb.de, conor+dt@kernel.org,
devicetree@vger.kernel.org, gordon.ge@bst.ai, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v3 6/8] arm64: dts: bst: add support for Black Sesame Technologies C1200 CDCU1.0 board
Date: Fri, 5 Sep 2025 09:23:48 +0200 [thread overview]
Message-ID: <179f19c0-d9fc-4efb-bc78-8dc1e7505b13@kernel.org> (raw)
In-Reply-To: <20250903070609.3475214-1-yangzh0906@thundersoft.com>
On 03/09/2025 09:06, Albert Yang wrote:
>>
>> No, you need to finally read and follow DTS coding style.
>>
>>> gic: interrupt-controller@32800000 {
>>> 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@32800000 {
> 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
next prev parent reply other threads:[~2025-09-05 7:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 12:31 [PATCH v3 0/8] Introduce Black Sesame Technologies C1200 SoC and CDCU1.0 board Albert Yang
2025-08-12 12:31 ` [PATCH v3 1/8] dt-bindings: vendor-prefixes: Add Black Sesame Technologies Co., Ltd Albert Yang
2025-08-12 13:34 ` Krzysztof Kozlowski
2025-08-13 4:53 ` Albert Yang
2025-08-13 6:01 ` Krzysztof Kozlowski
2025-08-13 11:37 ` Albert Yang
2025-08-12 12:31 ` [PATCH v3 2/8] dt-bindings: arm: add Black Sesame Technologies (bst) SoC Albert Yang
2025-08-12 13:35 ` Krzysztof Kozlowski
2025-08-12 12:31 ` [PATCH v3 3/8] arm64: Kconfig: add ARCH_BST for Black Sesame Technologies SoCs Albert Yang
2025-08-12 12:31 ` [PATCH v3 4/8] dt-bindings: mmc: add binding for BST DWCMSHC SDHCI controller Albert Yang
2025-08-14 8:50 ` Krzysztof Kozlowski
2025-08-12 12:31 ` [PATCH v3 5/8] mmc: sdhci: add Black Sesame Technologies BST C1200 controller driver Albert Yang
2025-08-18 10:48 ` Ulf Hansson
2025-08-18 12:08 ` Arnd Bergmann
2025-08-18 18:16 ` Adrian Hunter
2025-08-12 12:31 ` [PATCH v3 6/8] arm64: dts: bst: add support for Black Sesame Technologies C1200 CDCU1.0 board Albert Yang
2025-08-12 16:16 ` Krzysztof Kozlowski
2025-09-03 3:40 ` Albert Yang
2025-09-03 6:14 ` Krzysztof Kozlowski
[not found] ` <20250903070609.3475214-1-yangzh0906@thundersoft.com>
2025-09-05 7:23 ` Krzysztof Kozlowski [this message]
2025-08-12 12:31 ` [PATCH v3 7/8] arm64: defconfig: enable BST platform and SDHCI controller support Albert Yang
2025-08-12 13:38 ` Krzysztof Kozlowski
2025-08-12 12:31 ` [PATCH v3 8/8] MAINTAINERS: add and consolidate Black Sesame Technologies (BST) ARM SoC support Albert Yang
2025-08-12 13:33 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179f19c0-d9fc-4efb-bc78-8dc1e7505b13@kernel.org \
--to=krzk@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gordon.ge@bst.ai \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=yangzh0906@thundersoft.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).