From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: Lizhe <sensor1010@163.com>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, rmk+kernel@armlinux.org.uk,
jonas@kwiboo.se, david.wu@rock-chips.com
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: dwmac-rk: No need to check the return value of the phy_power_on()
Date: Wed, 15 Oct 2025 14:17:29 +0800 [thread overview]
Message-ID: <4c9ec1ab-8833-4e07-a39c-ba502117866f@rock-chips.com> (raw)
In-Reply-To: <20251015040847.6421-1-sensor1010@163.com>
On 10/15/2025 12:08 PM, Lizhe wrote:
> 'phy_power_on' is a local scope one within the driver, since the return
> value of the phy_power_on() function is always 0, checking its return
> value is redundant.
>
> the function name 'phy_power_on()' conflicts with the existing
> phy_power_on() function in the PHY subsystem. a suitable alternative
> name would be rk_phy_power_set(), particularly since when the second
> argument is false, this function actually powers off the PHY
>
> Signed-off-by: Lizhe <sensor1010@163.com>
> ---
> drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c | 17 ++++-------------
> 1 file changed, 4 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c b/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c
> index 51ea0caf16c1..9d296bfab013 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/dwmac-rk.c
> @@ -1461,23 +1461,18 @@ static int gmac_clk_enable(struct rk_priv_data *bsp_priv, bool enable)
> return 0;
> }
>
> -static int phy_power_on(struct rk_priv_data *bsp_priv, bool enable)
> +static void rk_phy_power_on(struct rk_priv_data *bsp_priv, bool enable)
> {
> struct regulator *ldo = bsp_priv->regulator;
> struct device *dev = bsp_priv->dev;
> - int ret;
>
> if (enable) {
> - ret = regulator_enable(ldo);
> - if (ret)
> + if (regulator_enable(ldo))
> dev_err(dev, "fail to enable phy-supply\n");
> } else {
> - ret = regulator_disable(ldo);
> - if (ret)
> + if (regulator_disable(ldo))
> dev_err(dev, "fail to disable phy-supply\n");
> }
> -
> - return 0;
> }
>
> static struct rk_priv_data *rk_gmac_setup(struct platform_device *pdev,
> @@ -1655,11 +1650,7 @@ static int rk_gmac_powerup(struct rk_priv_data *bsp_priv)
> dev_err(dev, "NO interface defined!\n");
> }
>
> - ret = phy_power_on(bsp_priv, true);
> - if (ret) {
> - gmac_clk_enable(bsp_priv, false);
Is gmac_clk_enable() also redundant?
> - return ret;
> - }
> + rk_phy_power_on(bsp_priv, true);
>
> pm_runtime_get_sync(dev);
>
--
Best,
Chaoyi
next prev parent reply other threads:[~2025-10-15 6:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 4:08 Lizhe
2025-10-15 6:17 ` Chaoyi Chen [this message]
2025-10-15 8:59 ` Simon Horman
2025-10-15 23:43 ` kernel test robot
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=4c9ec1ab-8833-4e07-a39c-ba502117866f@rock-chips.com \
--to=chaoyi.chen@rock-chips.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=david.wu@rock-chips.com \
--cc=edumazet@google.com \
--cc=jonas@kwiboo.se \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=sensor1010@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
all inboxes | Powered by JetHome®