From: Mathieu Othacehe <othacehe@gnu.org>
To: Conor Dooley <conor@kernel.org>
Cc: Primoz Fiser <primoz.fiser@norik.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Li Yang <leoyang.li@nxp.com>, Stefan Wahren <wahrenst@gmx.net>,
Christoph Stoidner <c.stoidner@phytec.de>,
Wadim Egorov <w.egorov@phytec.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, upstream@lists.phytec.de
Subject: Re: [PATCH v2 2/2] arm64: dts: imx93-phycore-segin: Add Phytec i.MX93 Segin
Date: Thu, 18 Jan 2024 14:43:07 +0100 [thread overview]
Message-ID: <87jzo6vjtg.fsf@gnu.org> (raw)
In-Reply-To: <20240118-regretful-viewer-8d7dfc7a0802@spud> (Conor Dooley's message of "Thu, 18 Jan 2024 10:19:23 +0000")
Hey,
> Please do not order properties alphabetically. Instead, please read
> the new documentation on property ordering that makes explicit what
> has just been convention until now:
> https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/tree/Documentation/devicetree/bindings/dts-coding-style.rst?h=for-next&id=83a368a3fc8ae8538bccb713dc0cae9eacc04790#n112
Thanks for the link.
I have a question though. Regarding that section:
--8<---------------cut here---------------start------------->8---
/* SD-Card */
&usdhc2 {
pinctrl-names = "default", "state_100mhz", "state_200mhz";
pinctrl-0 = <&pinctrl_usdhc2_default>, <&pinctrl_usdhc2_cd>;
pinctrl-1 = <&pinctrl_usdhc2_100mhz>, <&pinctrl_usdhc2_cd>;
pinctrl-2 = <&pinctrl_usdhc2_200mhz>, <&pinctrl_usdhc2_cd>;
bus-width = <4>;
cd-gpios = <&gpio3 00 GPIO_ACTIVE_LOW>;
no-sdio;
no-mmc;
vmmc-supply = <®_usdhc2_vmmc>;
status = "okay";
};
--8<---------------cut here---------------end--------------->8---
The documentation states:
--8<---------------cut here---------------start------------->8---
Order of Properties in Device Node
----------------------------------
The following order of properties in device nodes is preferred:
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
--8<---------------cut here---------------end--------------->8---
All of the properties in my example are falling into the "4" category I
guess, except for "status" that should come last. Now, how am I supposed
to order those properties? I had a look to other IMX device trees and it
is hard to establish a pattern. Pinctrl first, then alphabetical order?
Anything else?
Thanks for the guidance,
Mathieu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Mathieu Othacehe <othacehe@gnu.org>
To: Conor Dooley <conor@kernel.org>
Cc: Primoz Fiser <primoz.fiser@norik.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Li Yang <leoyang.li@nxp.com>, Stefan Wahren <wahrenst@gmx.net>,
Christoph Stoidner <c.stoidner@phytec.de>,
Wadim Egorov <w.egorov@phytec.de>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, upstream@lists.phytec.de
Subject: Re: [PATCH v2 2/2] arm64: dts: imx93-phycore-segin: Add Phytec i.MX93 Segin
Date: Thu, 18 Jan 2024 14:43:07 +0100 [thread overview]
Message-ID: <87jzo6vjtg.fsf@gnu.org> (raw)
In-Reply-To: <20240118-regretful-viewer-8d7dfc7a0802@spud> (Conor Dooley's message of "Thu, 18 Jan 2024 10:19:23 +0000")
Hey,
> Please do not order properties alphabetically. Instead, please read
> the new documentation on property ordering that makes explicit what
> has just been convention until now:
> https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git/tree/Documentation/devicetree/bindings/dts-coding-style.rst?h=for-next&id=83a368a3fc8ae8538bccb713dc0cae9eacc04790#n112
Thanks for the link.
I have a question though. Regarding that section:
--8<---------------cut here---------------start------------->8---
/* SD-Card */
&usdhc2 {
pinctrl-names = "default", "state_100mhz", "state_200mhz";
pinctrl-0 = <&pinctrl_usdhc2_default>, <&pinctrl_usdhc2_cd>;
pinctrl-1 = <&pinctrl_usdhc2_100mhz>, <&pinctrl_usdhc2_cd>;
pinctrl-2 = <&pinctrl_usdhc2_200mhz>, <&pinctrl_usdhc2_cd>;
bus-width = <4>;
cd-gpios = <&gpio3 00 GPIO_ACTIVE_LOW>;
no-sdio;
no-mmc;
vmmc-supply = <®_usdhc2_vmmc>;
status = "okay";
};
--8<---------------cut here---------------end--------------->8---
The documentation states:
--8<---------------cut here---------------start------------->8---
Order of Properties in Device Node
----------------------------------
The following order of properties in device nodes is preferred:
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
--8<---------------cut here---------------end--------------->8---
All of the properties in my example are falling into the "4" category I
guess, except for "status" that should come last. Now, how am I supposed
to order those properties? I had a look to other IMX device trees and it
is hard to establish a pattern. Pinctrl first, then alphabetical order?
Anything else?
Thanks for the guidance,
Mathieu
next prev parent reply other threads:[~2024-01-18 13:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 7:49 [PATCH v2 0/2] Add Phytec i.MX93 Segin support Mathieu Othacehe
2024-01-17 7:49 ` Mathieu Othacehe
2024-01-17 7:49 ` [PATCH v2 1/2] dt-bindings: arm: fsl: Add i.MX93 PHYTEC with Segin Mathieu Othacehe
2024-01-17 7:49 ` Mathieu Othacehe
2024-01-17 8:15 ` Krzysztof Kozlowski
2024-01-17 8:15 ` Krzysztof Kozlowski
2024-01-18 9:10 ` Primoz Fiser
2024-01-18 9:10 ` Primoz Fiser
2024-01-17 7:49 ` [PATCH v2 2/2] arm64: dts: imx93-phycore-segin: Add Phytec i.MX93 Segin Mathieu Othacehe
2024-01-17 7:49 ` Mathieu Othacehe
2024-01-18 9:58 ` Primoz Fiser
2024-01-18 9:58 ` Primoz Fiser
2024-01-18 10:19 ` Conor Dooley
2024-01-18 10:19 ` Conor Dooley
2024-01-18 13:43 ` Mathieu Othacehe [this message]
2024-01-18 13:43 ` Mathieu Othacehe
2024-01-18 15:56 ` Conor Dooley
2024-01-18 15:56 ` Conor Dooley
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=87jzo6vjtg.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=c.stoidner@phytec.de \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=primoz.fiser@norik.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.de \
--cc=wahrenst@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.