From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Louis-Alexis Eyraud <louisalexis.eyraud@collabora.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
kevin-kw.huang@airoha.com, macpaul.lin@mediatek.com,
matthias.bgg@gmail.com, kernel@collabora.com,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: phy: Introduce Airoha AN8801/R Gigabit Ethernet PHY driver
Date: Wed, 4 Mar 2026 16:32:10 +0000 [thread overview]
Message-ID: <aaheilkwpQ90xMmR@shell.armlinux.org.uk> (raw)
In-Reply-To: <20260304-add-airoha-an8801-support-v1-2-0ae4ee5a2f9d@collabora.com>
On Wed, Mar 04, 2026 at 10:35:29AM +0100, Louis-Alexis Eyraud wrote:
> +static void an8801r_get_wol(struct phy_device *phydev,
> + struct ethtool_wolinfo *wol)
> +{
> + u32 reg_val;
> +
> + air_buckpbus_reg_read(phydev, AN8801_BPBUS_REG_WAKEUP_CTL1, ®_val);
> +
> + wol->supported = WAKE_MAGIC;
> +
> + if (reg_val & AN8801_WOL_WAKE_MAGIC_EN)
> + wol->wolopts |= WAKE_MAGIC;
> + else
> + wol->wolopts &= ~WAKE_MAGIC;
Please only support WoL if you know that the PHY has been wired up in
such a way to allow it to actually wake the system. The PHY itself
merely supporting WoL is insufficient.
Please look at my recent change to realtek_main.c in commit
b826bf795564 ("net: phy: realtek: fix RTL8211F wake-on-lan support")
to see a possible way to achieve this.
> +static int an8801r_config_init(struct phy_device *phydev)
> +{
> + u8 led_default_function[AN8801R_NUM_LEDS] = { 0 };
> + int prev_page, ret;
> +
> + ret = an8801r_of_init_leds(phydev, led_default_function);
> + if (ret)
> + return ret;
> +
> + /* Disable Low Power Mode (LPM) */
> + ret = phy_write_mmd(phydev, MDIO_MMD_VEND2, AN8801_REG_PHY_INTERNAL0,
> + FIELD_PREP(AN8801_PHY_INTFUNC_MASK, 0x1e));
> + if (ret)
> + return ret;
> +
> + ret = phy_write_mmd(phydev, MDIO_MMD_VEND2, AN8801_REG_PHY_INTERNAL1,
> + FIELD_PREP(AN8801_PHY_INTFUNC_MASK, 0x2));
> + if (ret)
> + return ret;
> +
> + /* Disable EEE by default */
> + ret = phy_write_mmd(phydev, MDIO_MMD_AN, MDIO_AN_EEE_ADV, 0);
> + if (ret)
> + return ret;
Are you sure this is safe, e.g. over a suspend/resume, and doesn't
cause the hardware vs software state to desync?
> +
> + prev_page = phy_select_page(phydev, AIR_PHY_PAGE_EXTENDED_1);
> + if (prev_page < 0)
> + return prev_page;
No, this is buggy. Please read the phy_select_page() documentation to
find out why.
> +
> + /* Set the PHY to perform auto-downshift after 3 auto-negotiation
> + * attempts
> + */
> + __phy_write(phydev, AN8801_EXT_REG_PHY,
> + FIELD_PREP(AN8801_EXT_PHY_CTRL1, 0x1d) |
> + FIELD_PREP(AN8801_EXT_PHY_DOWNSHIFT_CTL, 1) |
> + AN8801_EXT_PHY_DOWNSHIFT_EN);
> +
> + ret = phy_restore_page(phydev, prev_page, ret);
> + if (ret)
> + return ret;
However, the bug could've been avoided by using the appropriate
accessor:
ret = phy_write_paged(phydev, AIR_PHY_PAGE_EXTENDED_1,
AN8801_EXT_REG_PHY,
FIELD_PREP(AN8801_EXT_PHY_CTRL1, 0x1d) |
FIELD_PREP(AN8801_EXT_PHY_DOWNSHIFT_CTL, 1) |
AN8801_EXT_PHY_DOWNSHIFT_EN);
if (ret < 0)
return ret;
> +static int an8801r_read_status(struct phy_device *phydev)
> +{
> + int prev_speed, ret;
> + u32 val;
> +
> + prev_speed = phydev->speed;
> +
> + ret = genphy_read_status(phydev);
> + if (ret)
> + return ret;
> +
> + if (!phydev->link)
> + return 0;
> +
> + if (prev_speed != phydev->speed) {
Maybe:
if (phydev->link && prev_speed != phydev->speed) {
?
Thanks.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2026-03-04 16:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 9:35 [PATCH net-next 0/2] Introduce Airoha AN8801R series Gigabit Ethernet PHY driver Louis-Alexis Eyraud
2026-03-04 9:35 ` [PATCH net-next 1/2] dt-bindings: net: Add support for Airoha AN8801/R GbE PHY Louis-Alexis Eyraud
2026-03-04 10:14 ` Maxime Chevallier
2026-03-05 8:59 ` Louis-Alexis Eyraud
2026-03-12 13:48 ` Rob Herring (Arm)
2026-03-04 9:35 ` [PATCH net-next 2/2] net: phy: Introduce Airoha AN8801/R Gigabit Ethernet PHY driver Louis-Alexis Eyraud
2026-03-04 9:58 ` Maxime Chevallier
2026-03-06 15:29 ` Louis-Alexis Eyraud
2026-03-04 14:59 ` Andrew Lunn
2026-03-25 18:15 ` Louis-Alexis Eyraud
2026-03-25 19:45 ` Andrew Lunn
2026-03-04 16:32 ` Russell King (Oracle) [this message]
2026-03-25 14:44 ` Louis-Alexis Eyraud
2026-03-04 22:13 ` 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=aaheilkwpQ90xMmR@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@collabora.com \
--cc=kevin-kw.huang@airoha.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louisalexis.eyraud@collabora.com \
--cc=macpaul.lin@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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