Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: Zhyi <zyheihei_123@163.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [RFC PATCH v2] arm64: dts: rockchip: H28K: release RTL8211F reset before MDIO probing
Date: Mon, 03 Aug 2026 16:54:12 +0000	[thread overview]
Message-ID: <20260803165413.AE81C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <178577533421.26919.15449256732994709630.h28k-rfc-v2@163.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The pinctrl configuration for the PHY reset GPIO (`&gmac1_rstn_l`) was incorrectly left on the PHY node after the `reset-gpios` control was moved to the MDIO bus node, resulting in the pinmux being applied too late.
--

--- Patch [1]: [RFC PATCH v2] arm64: dts: rockchip: H28K: release RTL8211F reset before MDIO probing ---
commit ed5c8c6d0629795b93f02fb617db0f38d4725c0d
Author: Zhyi <zyheihei_123@163.com>

arm64: dts: rockchip: H28K: release RTL8211F reset before MDIO probing

Move the reset-gpios property to the MDIO bus level to ensure the RTL8211F
PHY is released from reset before scanning the bus. This fixes an issue
where the PHY cannot be found during probe.

> diff --git a/arch/arm64/boot/dts/rockchip/rk3528-hinlink-h28k.dts b/arch/arm64/boot/dts/rockchip/rk3528-hinlink-h28k.dts
> index 0ec50e9156eb1..7ba3fa46c8610 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3528-hinlink-h28k.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3528-hinlink-h28k.dts
[ ... ]
>  &mdio1 {
> +	reset-gpios = <&gpio4 RK_PC2 GPIO_ACTIVE_LOW>;
> +	reset-delay-us = <20000>;
> +	reset-post-delay-us = <100000>;
>  	rgmii_phy: ethernet-phy@1 {
>  		compatible = "ethernet-phy-ieee802.3-c22";
>  		reg = <0x1>;
>  		pinctrl-names = "default";
>  		pinctrl-0 = <&gmac1_rstn_l>;

[Severity: Medium]
Will this pinctrl configuration be applied too late since it was left on the
PHY node?

During initialization, mdiobus_register() parses reset-gpios from the &mdio1
node and toggles it before scanning for PHY devices on the bus.

The driver core only applies a device's pinctrl when that specific device
is probed. Since the PHY device is only created and probed after the MDIO
bus scan successfully discovers it, the pinctrl configuration is applied
after the reset phase has already completed.

Should the pinctrl-0 = <&gmac1_rstn_l> property also be moved to the parent
&gmac1 node to ensure it is applied before the MDIO bus reset sequence?

> -		reset-assert-us = <20000>;
> -		reset-deassert-us = <100000>;
> -		reset-gpios = <&gpio4 RK_PC2 GPIO_ACTIVE_LOW>;
>  	};
>  };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/178577533421.26919.15449256732994709630.h28k-rfc-v2@163.com?part=1

  reply	other threads:[~2026-08-03 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 10:46 [RFC PATCH] arm64: dts: rockchip: H28K: release RTL8211F reset before MDIO probing Zhyi
2026-08-03 11:10 ` sashiko-bot
2026-08-03 12:40 ` Chukun Pan
2026-08-03 16:42 ` [RFC PATCH v2] " Zhyi
2026-08-03 16:54   ` sashiko-bot [this message]
2026-08-03 18:16   ` Jonas Karlman
2026-08-03 23:49     ` Zhyi

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=20260803165413.AE81C1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=zyheihei_123@163.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