[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7f8679f7-5450-438c-98d7-06ca09cebbcd@lunn.ch>
Date: Thu, 22 Aug 2024 18:13:02 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Jijie Shao <shaojijie@...wei.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, shenjian15@...wei.com, wangpeiyang1@...wei.com,
liuyonglong@...wei.com, sudongming1@...wei.com,
xujunsheng@...wei.com, shiyongbang@...wei.com, libaihan@...wei.com,
jdamato@...tly.com, horms@...nel.org, jonathan.cameron@...wei.com,
shameerali.kolothum.thodi@...wei.com, salil.mehta@...wei.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V3 net-next 03/11] net: hibmcge: Add mdio and hardware
configuration supported in this module
> +void hbg_phy_start(struct hbg_priv *priv)
> +{
> + if (!priv->mac.phydev)
> + return;
> +
> + phy_start(priv->mac.phydev);
> +}
> +
> +void hbg_phy_stop(struct hbg_priv *priv)
> +{
> + if (!priv->mac.phydev)
> + return;
> +
> + phy_stop(priv->mac.phydev);
Can this condition priv->mac.phydev not be true? The mdio bus setup
and connecting to the PHY seems to be unconditional. If it fails, the
driver fails to probe.
Andrew
Powered by blists - more mailing lists