From: Christoph Niedermaier <cniedermaier@dh-electronics.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Peng Fan <peng.fan@nxp.com>, Shawn Guo <shawnguo@kernel.org>,
Marek Vasut <marex@denx.de>, Fabio Estevam <festevam@denx.de>,
NXP Linux Team <linux-imx@nxp.com>,
kernel <kernel@dh-electronics.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 2/4] ARM: dts: imx6ull-dhcom: Add DH electronics DHCOM i.MX6ULL SoM and PDK2 board
Date: Thu, 17 Nov 2022 16:27:34 +0000 [thread overview]
Message-ID: <ea79b347008948aeb3a9ecb897ed0e64@dh-electronics.com> (raw)
In-Reply-To: <2bc5b167-a453-bbb4-9feb-c03913874740@linaro.org>
From: Krzysztof Kozlowski [mailto:krzysztof.kozlowski@linaro.org]
Sent: Thursday, November 17, 2022 3:39 PM
> On 17/11/2022 15:11, Christoph Niedermaier wrote:
>>>> +&fec2 { /* DHCOM ETH2 */
>>>> + phy-handle = <&mdio2_phy1>;
>>>> + phy-mode = "rmii";
>>>> + pinctrl-0 = <&pinctrl_fec2>;
>>>> + pinctrl-names = "default";
>>>> + status = "okay";
>>>> +
>>>> + mdio {
>>>> + #address-cells = <1>;
>>>> + #size-cells = <0>;
>>>> +
>>>> + mdio2_phy0: ethernet-phy@0 { /* SMSC LAN8710Ai */
>>>> + clock-names = "rmii-ref";
>>>> + clocks = <&clks IMX6UL_CLK_ENET_REF>;
>>>> + compatible = "ethernet-phy-id0007.c0f0",
>>>> + "ethernet-phy-ieee802.3-c22";
>>>> + interrupt-parent = <&gpio5>;
>>>> + interrupts = <5 IRQ_TYPE_LEVEL_LOW>;
>>>> + pinctrl-0 = <&pinctrl_fec1_phy &pinctrl_snvs_fec1_phy>;
>>>> + pinctrl-names = "default";
>>>> + reg = <0>;
>>>
>>> compatible first, reg second, then the rest of properties. Same in other
>>> places.
>>
>> Sorry, I have sorted it alphabetically.
>> Should the status property be sorted at the end or also alphabetically?
>
> You do not have status here. For the cases where it is present, depends
> on the preferences of subarch maintainer. Usually it also goes to the
> end, but not always.
Thanks for the clarification.
Regards
Christoph
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-17 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 10:31 [PATCH 0/4] ARM: dts: imx6ull-dhcom: Add DH electronics DHCOM i.MX6ULL SoM support Christoph Niedermaier
2022-11-17 10:31 ` [PATCH 1/4] dt-bindings: arm: fsl: Add PDK2, PicoITX and DRC02 boards for the DHCOM i.MX6ULL SoM Christoph Niedermaier
2022-11-17 13:05 ` Krzysztof Kozlowski
2022-11-17 10:31 ` [PATCH 2/4] ARM: dts: imx6ull-dhcom: Add DH electronics DHCOM i.MX6ULL SoM and PDK2 board Christoph Niedermaier
2022-11-17 13:09 ` Krzysztof Kozlowski
2022-11-17 14:11 ` Christoph Niedermaier
2022-11-17 14:38 ` Krzysztof Kozlowski
2022-11-17 16:27 ` Christoph Niedermaier [this message]
2022-11-17 10:31 ` [PATCH 3/4] ARM: dts: imx6ull-dhcom: Add DHCOM based PicoITX board Christoph Niedermaier
2022-11-17 10:31 ` [PATCH 4/4] ARM: dts: imx6ull-dhcom: Add DHSOM based DRC02 board Christoph Niedermaier
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=ea79b347008948aeb3a9ecb897ed0e64@dh-electronics.com \
--to=cniedermaier@dh-electronics.com \
--cc=festevam@denx.de \
--cc=kernel@dh-electronics.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=marex@denx.de \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=shawnguo@kernel.org \
/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