From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Marek Vasut <marex@denx.de>, <linux-arm-kernel@lists.infradead.org>
Cc: Christophe Roullier <christophe.roullier@foss.st.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh@kernel.org>, <devicetree@vger.kernel.org>,
<kernel@dh-electronics.com>,
<linux-stm32@st-md-mailman.stormreply.com>
Subject: Re: [PATCH v2] ARM: dts: stm32: Add ethernet support for DH STM32MP13xx DHCOR DHSBC board
Date: Fri, 28 Jun 2024 08:44:07 +0200 [thread overview]
Message-ID: <04d2ef05-4f47-445c-8f5c-1e550ef5aff2@foss.st.com> (raw)
In-Reply-To: <20240628005729.119871-1-marex@denx.de>
Hi Marek
On 6/28/24 02:57, Marek Vasut wrote:
> Add ethernet support for the DH STM32MP13xx DHCOR DHSBC carrier board.
> This carrier board is populated with two gigabit ethernet ports and two
> Realtek RTL8211F PHYs, both are described in this DT patch.
>
> Signed-off-by: Marek Vasut <marex@denx.de>
I already applied series which add the ETH support in mp13 DH board. Can
you please resend a patch which only add the nvmem efuse stuff please ?
Alex
> ---
> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
> Cc: Christophe Roullier <christophe.roullier@foss.st.com>
> Cc: Conor Dooley <conor+dt@kernel.org>
> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
> Cc: Rob Herring <robh@kernel.org>
> Cc: devicetree@vger.kernel.org
> Cc: kernel@dh-electronics.com
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-stm32@st-md-mailman.stormreply.com
> ---
> V2: Fold ARM: dts: stm32: Add phandle to nvmem efuse into STM32MP13xx ethernet
> DT node into this patch and make the nvmem-cells/nvmem-cell-names specific
> to this board
> ---
> .../boot/dts/st/stm32mp135f-dhcor-dhsbc.dts | 60 +++++++++++++++++++
> 1 file changed, 60 insertions(+)
>
> diff --git a/arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dts b/arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dts
> index 5f4f6b6e427a5..3cc9ad88d61bc 100644
> --- a/arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dts
> +++ b/arch/arm/boot/dts/st/stm32mp135f-dhcor-dhsbc.dts
> @@ -22,6 +22,8 @@ / {
> "st,stm32mp135";
>
> aliases {
> + ethernet0 = ðernet1;
> + ethernet1 = ðernet2;
> serial2 = &usart1;
> serial3 = &usart2;
> };
> @@ -72,6 +74,64 @@ channel@12 {
> };
> };
>
> +ðernet1 {
> + nvmem-cell-names = "mac-address";
> + nvmem-cells = <ðernet_mac1_address>;
> + phy-handle = <ðphy1>;
> + phy-mode = "rgmii-id";
> + pinctrl-0 = <ð1_rgmii_pins_a>;
> + pinctrl-1 = <ð1_rgmii_sleep_pins_a>;
> + pinctrl-names = "default", "sleep";
> + st,ext-phyclk;
> + status = "okay";
> +
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "snps,dwmac-mdio";
> +
> + ethphy1: ethernet-phy@1 {
> + /* RTL8211F */
> + compatible = "ethernet-phy-id001c.c916";
> + interrupt-parent = <&gpiog>;
> + interrupts = <12 IRQ_TYPE_LEVEL_LOW>;
> + reg = <1>;
> + reset-assert-us = <15000>;
> + reset-deassert-us = <55000>;
> + reset-gpios = <&gpioa 11 GPIO_ACTIVE_LOW>;
> + };
> + };
> +};
> +
> +ðernet2 {
> + nvmem-cell-names = "mac-address";
> + nvmem-cells = <ðernet_mac2_address>;
> + phy-handle = <ðphy2>;
> + phy-mode = "rgmii-id";
> + pinctrl-0 = <ð2_rgmii_pins_a>;
> + pinctrl-1 = <ð2_rgmii_sleep_pins_a>;
> + pinctrl-names = "default", "sleep";
> + st,ext-phyclk;
> + status = "okay";
> +
> + mdio {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "snps,dwmac-mdio";
> +
> + ethphy2: ethernet-phy@1 {
> + /* RTL8211F */
> + compatible = "ethernet-phy-id001c.c916";
> + interrupt-parent = <&gpiog>;
> + interrupts = <15 IRQ_TYPE_LEVEL_LOW>;
> + reg = <1>;
> + reset-assert-us = <15000>;
> + reset-deassert-us = <55000>;
> + reset-gpios = <&gpiog 8 GPIO_ACTIVE_LOW>;
> + };
> + };
> +};
> +
> &gpioa {
> gpio-line-names = "", "", "", "",
> "", "DHSBC_USB_PWR_CC1", "", "",
next prev parent reply other threads:[~2024-06-28 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 0:57 [PATCH v2] ARM: dts: stm32: Add ethernet support for DH STM32MP13xx DHCOR DHSBC board Marek Vasut
2024-06-28 6:44 ` Alexandre TORGUE [this message]
2024-06-30 1:36 ` Marek Vasut
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=04d2ef05-4f47-445c-8f5c-1e550ef5aff2@foss.st.com \
--to=alexandre.torgue@foss.st.com \
--cc=christophe.roullier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@dh-electronics.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).