From: Andrew Lunn <andrew@lunn.ch>
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>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
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 15:59:43 +0100 [thread overview]
Message-ID: <3fbfabf7-b3af-405b-ade4-4f62db2c1c45@lunn.ch> (raw)
In-Reply-To: <20260304-add-airoha-an8801-support-v1-2-0ae4ee5a2f9d@collabora.com>
> +static int an8801r_did_interrupt(struct phy_device *phydev)
> +{
> + u32 irq_en, irq_status;
> + int ret;
> +
> + ret = air_buckpbus_reg_read(phydev, AN8801_BPBUS_REG_WAKE_IRQ_EN,
> + &irq_en);
> + if (ret)
> + return ret;
> +
> + ret = air_buckpbus_reg_read(phydev, AN8801_BPBUS_REG_WAKE_IRQ_STS,
> + &irq_status);
> + if (ret)
> + return ret;
> +
> + if (irq_status & AN8801_IRQ_WAKE_MAGICPKT)
> + return 0;
With a name like an8801r_did_interrupt() you would expect the return
value to be some value of True, if there was an interrupt. I would
suggest either a different name, or return 1. Maybe also add a
kerneldoc header indicating the return values, since it is probably
not going to be standard.
> +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;
How does WoL work on this device. Only via interrupts? If so, maybe
you should only return WAKE_MAGIC as supported if there is a valid
interrupt?
> +static int an8801r_rgmii_delay_config(struct phy_device *phydev)
> +{
> + switch (phydev->interface) {
> + case PHY_INTERFACE_MODE_RGMII_TXID:
> + return an8801r_rgmii_txdelay(phydev, 4);
> + case PHY_INTERFACE_MODE_RGMII_RXID:
> + return an8801r_rgmii_rxdelay(phydev, 0);
> + case PHY_INTERFACE_MODE_RGMII_ID:
> + return an8801r_rgmii_txdelay(phydev, 4);
> + return an8801r_rgmii_rxdelay(phydev, 0);
The parameters look very odd here. 4 means 2ns, but 0 also means 0ns?
Can this API be improved?
Also, PHY_INTERFACE_MODE_RGMII_TXID means 2ns delay for TX, but it
also means 0ns delay for RX. The code appears to be missing this
second part.
> + case PHY_INTERFACE_MODE_RGMII:
And here you should be disabling all delays. We have seen boards where
the strapping is wrong, the PHY boots in RGMII_ID, but RGMII is
required, and so the driver must fully implement
PHY_INTERFACE_MODE_RGMII disabling the delays.
> +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;
Why? If EEE is broken, this is not sufficient to stop a user
re-enabling it.
> +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;
You configure the PHY to support downshift. If it has performed a
downshift, does it report the actual speed in the usual registers read
by genphy_read_status(), or is it necessary to read a vendor register?
> +static struct phy_driver airoha_driver[] = {
> +{
> + PHY_ID_MATCH_MODEL(AN8801R_PHY_ID),
> + .name = "Airoha AN8801R",
> + .features = PHY_GBIT_FEATURES,
Should not be needed, if the PHY enumerates its capabilities
correctly.
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2026-03-04 15:00 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 " 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 [this message]
2026-03-25 18:15 ` Louis-Alexis Eyraud
2026-03-25 19:45 ` Andrew Lunn
2026-03-04 16:32 ` Russell King (Oracle)
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=3fbfabf7-b3af-405b-ade4-4f62db2c1c45@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@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=linux@armlinux.org.uk \
--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
all inboxes | Powered by JetHome®