From: Detlev Casanova <detlev.casanova@collabora.com>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Dragan Simic <dsimic@manjaro.org>,
Chris Morgan <macromorgan@hotmail.com>,
Kever Yang <kever.yang@rock-chips.com>,
Tim Lunn <tim@feathertop.org>, FUKAUMI Naoki <naoki@radxa.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
Weizhao Ouyang <weizhao.ouyang@arm.com>,
Elon Zhang <zhangzj@rock-chips.com>,
Alexey Charkov <alchark@gmail.com>,
Stephen Chen <stephen@radxa.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, kernel@collabora.com
Subject: Re: [PATCH v2 2/2] arm64: dts: rockchip: Add Radxa ROCK 4D device tree
Date: Thu, 13 Feb 2025 14:56:48 -0500 [thread overview]
Message-ID: <5973630.DvuYhMxLoT@trenzalore> (raw)
In-Reply-To: <b5977d21-aa39-4e91-863b-cc7f9dc6938c@kwiboo.se>
Hi Jonas,
On Thursday, 13 February 2025 10:48:10 EST Jonas Karlman wrote:
> Hi Detlev,
>
> On 2025-02-13 15:57, Detlev Casanova wrote:
> > From: Stephen Chen <stephen@radxa.com>
> >
> > The Radxa ROCK 4D board is based on the Rockchip rk3576 SoC.
> >
> > The device tree adds support for basic devices:
> > - UART
> > - SD Card
> > - Ethernet
> > - USB
> > - RTC
> >
> > It has 4 USB ports but only 3 are usable as the top left one is used
> > for maskrom.
> >
> > It has a USB-C port that is only used for powering the board.
> >
> > Signed-off-by: Stephen Chen <stephen@radxa.com>
> > Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
> > ---
> >
> > arch/arm64/boot/dts/rockchip/Makefile | 1 +
> > .../boot/dts/rockchip/rk3576-rock-4d.dts | 651 ++++++++++++++++++
> > 2 files changed, 652 insertions(+)
> > create mode 100644 arch/arm64/boot/dts/rockchip/rk3576-rock-4d.dts
> >
> > diff --git a/arch/arm64/boot/dts/rockchip/Makefile
> > b/arch/arm64/boot/dts/rockchip/Makefile index
> > def1222c1907e..a112aeb37948a 100644
> > --- a/arch/arm64/boot/dts/rockchip/Makefile
> > +++ b/arch/arm64/boot/dts/rockchip/Makefile
> > @@ -132,6 +132,7 @@ dtb-$(CONFIG_ARCH_ROCKCHIP) +=
> > rk3568-wolfvision-pf5-display-vz.dtbo>
> > dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3568-wolfvision-pf5-io-expander.dtbo
> > dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3576-armsom-sige5.dtb
> > dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3576-evb1-v10.dtb
> >
> > +dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3576-rock-4d.dtb
> >
> > dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3582-radxa-e52c.dtb
> > dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3588-armsom-sige7.dtb
> > dtb-$(CONFIG_ARCH_ROCKCHIP) += rk3588-armsom-w3.dtb
> >
> > diff --git a/arch/arm64/boot/dts/rockchip/rk3576-rock-4d.dts
> > b/arch/arm64/boot/dts/rockchip/rk3576-rock-4d.dts new file mode 100644
> > index 0000000000000..f356742f9d643
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/rockchip/rk3576-rock-4d.dts
> > @@ -0,0 +1,651 @@
>
> [snip]
>
> > +&gmac0 {
> > + phy-mode = "rgmii-id";
> > + clock_in_out = "output";
> > +
> > + snps,reset-gpio = <&gpio2 RK_PB5 GPIO_ACTIVE_LOW>;
> > + snps,reset-active-low;
> > + snps,reset-delays-us = <0 20000 100000>;
>
> The snps,reset- props are deprecated and should be changed to reset-
> props in the phy node.
Arg, second time I use deprectated props on new things. Are there plans or
ways to make dtbs_check warn about those ?
> > +
> > + pinctrl-names = "default";
> > + pinctrl-0 = <ð0m0_miim
> > + ð0m0_tx_bus2
> > + ð0m0_rx_bus2
> > + ð0m0_rgmii_clk
> > + ð0m0_rgmii_bus
> > + ðm0_clk0_25m_out>;
> > +
> > + phy-handle = <&rgmii_phy0>;
> > + status = "okay";
> > +};
>
> [snip]
>
> > +&mdio0 {
> > + rgmii_phy0: phy@1 {
>
> Maybe ethernet-phy@1 ?
Indeed.
> > + compatible = "ethernet-phy-ieee802.3-c22";
> > + reg = <0x1>;
> > + clocks = <&cru REFCLKO25M_GMAC0_OUT>;
>
> Please add reset- props here.
>
> Changing to use reset- props may cause issue if a RTL8211F PHY is used
> on the board. Use a ethernet-phy-id compatible or mainline U-Boot to
> ensure the Ethernet PHY can be discovered during probe.
Using downstream u-boot, with the RTL8211F PHY, linux can still detect the PHY
and use it correctly, even with reset-* props at the PHY level.
I guess I can keep those there then, unless the issues you mention are more
subtle than that ?
Detlev.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-02-13 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 14:57 [PATCH v2 0/2] Add Radxa Rock 4D support Detlev Casanova
2025-02-13 14:57 ` [PATCH v2 1/2] dt-bindings: arm: rockchip: Add Radxa ROCK 4D board Detlev Casanova
2025-02-14 8:32 ` Krzysztof Kozlowski
2025-02-13 14:57 ` [PATCH v2 2/2] arm64: dts: rockchip: Add Radxa ROCK 4D device tree Detlev Casanova
2025-02-13 15:48 ` Jonas Karlman
2025-02-13 19:56 ` Detlev Casanova [this message]
2025-02-13 20:19 ` Jonas Karlman
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=5973630.DvuYhMxLoT@trenzalore \
--to=detlev.casanova@collabora.com \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--cc=kernel@collabora.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=michael.riesch@wolfvision.net \
--cc=naoki@radxa.com \
--cc=robh@kernel.org \
--cc=stephen@radxa.com \
--cc=tim@feathertop.org \
--cc=weizhao.ouyang@arm.com \
--cc=zhangzj@rock-chips.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