From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Shawn Guo" <shawnguo2@yeah.net>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.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>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<imx@lists.linux.dev>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 2/3] ARM: dts: imx6ul: Add Variscite VAR-SOM-MX6UL SoM support
Date: Mon, 03 Mar 2025 15:46:52 +0100 [thread overview]
Message-ID: <D86POCANGF07.3HE2LVK396FGX@bootlin.com> (raw)
In-Reply-To: <Z7njGg4Hhc4wcZHU@dragon>
Hi Shawn,
On Sat Feb 22, 2025 at 3:45 PM CET, Shawn Guo wrote:
[...]
>> + reg_gpio_dvfs: reg-gpio-dvfs {
>> + compatible = "regulator-gpio";
>> + regulator-min-microvolt = <1300000>;
>> + regulator-max-microvolt = <1400000>;
>> + regulator-name = "gpio_dvfs";
>> + regulator-type = "voltage";
>> + gpios = <&gpio4 13 GPIO_ACTIVE_HIGH>;
>
> Don't we need 'enable-active-high'?
I am not specifying 'enable-gpios' but 'gpios' here so from my understanding of
gpio-regulator.yaml and examples from other device trees I don't think so.
>> + states = <1300000 0x1 1400000 0x0>;
>> + };
>> +
>> + rmii_ref_clk: rmii-ref-clk-grp {
>
> What does "-grp" in node name mean?
A mistake on my side, I will rename the label to "rmii-ref-clk".
>> + compatible = "fixed-clock";
>> + clock-output-names = "rmii-ref";
>> + };
>> +};
>> +
>> +&cpu0 {
>> + dc-supply = <®_gpio_dvfs>;
>> +};
>> +
>> +&clks {
>> + assigned-clocks = <&clks IMX6UL_CLK_PLL4_AUDIO_DIV>;
>> + assigned-clock-rates = <786432000>;
>> +};
>> +
>> +&fec1 {
>> + pinctrl-names = "default";
>> + pinctrl-0 = <&pinctrl_enet1>, <&pinctrl_enet1_gpio>, <&pinctrl_enet1_mdio>;
>> + phy-mode = "rmii";
>> + phy-reset-gpios = <&gpio5 0 GPIO_ACTIVE_LOW>;
>> + phy-reset-duration = <100>;
>> + phy-handle = <ðphy0>;
>> + status = "okay";
>> +
>> + mdio {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + ethphy0: ethernet-phy@1 {
>> + compatible = "ethernet-phy-ieee802.3-c22";
>> + micrel,rmii-reference-clock-select-25-mhz = <1>;
>> + micrel,led-mode = <1>;
>> + clocks = <&rmii_ref_clk>;
>> + clock-names = "rmii-ref";
>> + reg = <1>;
>
> We generally sort properties like:
>
> - compatible
> - reg
> - generic ones
> - vendor prefixed ones
>
> So in this case, we will get:
>
> compatible = "ethernet-phy-ieee802.3-c22";
> reg = <1>;
> clocks = <&rmii_ref_clk>;
> clock-names = "rmii-ref";
> micrel,rmii-reference-clock-select-25-mhz = <1>;
> micrel,led-mode = <1>;
Thanks for clarifying that! I will revise this for the next version.
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2025-03-03 14:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 15:30 [PATCH v2 0/3] Add Variscite i.MX6UL SoM and Concerto board support Antonin Godard
2025-01-27 15:31 ` [PATCH v2 1/3] dt-bindings: arm: fsl: Add VAR-SOM-MX6UL SoM and Concerto board Antonin Godard
2025-01-27 17:51 ` Conor Dooley
2025-01-27 15:31 ` [PATCH v2 2/3] ARM: dts: imx6ul: Add Variscite VAR-SOM-MX6UL SoM support Antonin Godard
2025-02-22 14:45 ` Shawn Guo
2025-03-03 14:46 ` Antonin Godard [this message]
2025-01-27 15:31 ` [PATCH v2 3/3] ARM: dts: imx6ul: Add Variscite Concerto board support Antonin Godard
2025-02-22 14:52 ` Shawn Guo
2025-02-14 9:09 ` [PATCH v2 0/3] Add Variscite i.MX6UL SoM and " Antonin Godard
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=D86POCANGF07.3HE2LVK396FGX@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo2@yeah.net \
--cc=shawnguo@kernel.org \
--cc=thomas.petazzoni@bootlin.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 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.