[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f6c63297-a246-4daa-b47b-464c844baedb@lunn.ch>
Date: Fri, 28 Feb 2025 15:10:10 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Frank Sae <Frank.Sae@...or-comm.com>
Cc: Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, netdev@...r.kernel.org,
Masahiro Yamada <masahiroy@...nel.org>,
Parthiban.Veerasooran@...rochip.com, linux-kernel@...r.kernel.org,
xiaogang.fan@...or-comm.com, fei.zhang@...or-comm.com,
hua.sun@...or-comm.com
Subject: Re: [PATCH net-next v3 06/14] motorcomm:yt6801: Implement the
fxgmac_start function
> +static int fxgmac_phy_connect(struct fxgmac_pdata *priv)
> +{
> + struct phy_device *phydev = priv->phydev;
> + int ret;
> +
> + priv->phydev->irq = PHY_POLL;
> + ret = phy_connect_direct(priv->netdev, phydev, fxgmac_phylink_handler,
> + PHY_INTERFACE_MODE_INTERNAL);
> + if (ret)
> + return ret;
> +
> + phy_support_asym_pause(phydev);
> + priv->phydev->mac_managed_pm = 1;
> + phy_attached_info(phydev);
> +
> + return 0;
> +}
Please consider swapping to phylink, not phylib. Your current pause
implementation is broken, which is a common problem with drivers using
phylib. phylink makes it much harder to get pause wrong. The same can
be said for EEE, if you decide to implement it.
Andrew
Powered by blists - more mailing lists