From: Oleksij Rempel <o.rempel@pengutronix.de>
To: "Jens Emil Schulz Østergaard" <jensemil.schulzostergaard@microchip.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Daniel Machon <daniel.machon@microchip.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@pengutronix.de, rsc@pengutronix.de
Subject: Re: [PATCH net-next] net: phy: micrel: Add support for lan9645x internal phy
Date: Fri, 23 Jan 2026 10:55:56 +0100 [thread overview]
Message-ID: <aXNFrDOdPanZ_cjk@pengutronix.de> (raw)
In-Reply-To: <20260123-phy_micrel_add_support_for_lan9645x_internal_phy-v1-1-8484b1a5a7fd@microchip.com>
Hi Jens,
On Fri, Jan 23, 2026 at 08:50:55AM +0100, Jens Emil Schulz Østergaard wrote:
> LAN9645X is a family of switch chips with 5 internal copper phys. The
> internal PHY is based on parts of LAN8832. This is a low-power, single
> port triple-speed (10BASE-T/100BASE-TX/1000BASE-T) ethernet physical
> layer transceiver (PHY) that supports transmission and reception of data
> on standard CAT-5, as well as CAT-5e and CAT-6 Unshielded Twisted
> Pair (UTP) cables.
>
> Add support for the internal PHY of the lan9645x chip family.
Looks like interesting switch for our use cases :)
> Reviewed-by: Steen Hegelund <Steen.Hegelund@microchip.com>
> Reviewed-by: Daniel Machon <daniel.machon@microchip.com>
> Signed-off-by: Jens Emil Schulz Østergaard <jensemil.schulzostergaard@microchip.com>
> ---
> drivers/net/phy/micrel.c | 142 +++++++++++++++++++++++++++++++++++++++++++++
> include/linux/micrel_phy.h | 1 +
> 2 files changed, 143 insertions(+)
>
> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
> index 225d4adf28be..7f47f7987067 100644
> --- a/drivers/net/phy/micrel.c
> +++ b/drivers/net/phy/micrel.c
> @@ -6502,6 +6502,132 @@ static void lan8842_get_phy_stats(struct phy_device *phydev,
> stats->tx_errors = priv->phy_stats.tx_errors;
> }
>
> +#define LAN9645X_DAC_ICAS_AMP_POWER_DOWN 0x47
> +#define LAN9645X_BTRX_QBIAS_POWER_DOWN 0x46
> +#define LAN9645X_TX_LOW_I_CH_CD_POWER_MGMT 0x45
> +#define LAN9645X_TX_LOW_I_CH_B_POWER_MGMT 0x44
> +#define LAN9645X_TX_LOW_I_CH_A_POWER_MGMT 0x43
> +static const struct lanphy_reg_data force_dac_tx_errata[] = {
> + /* Force channel A/B/C/D TX on */
> + { LAN8814_PAGE_POWER_REGS,
> + LAN9645X_DAC_ICAS_AMP_POWER_DOWN,
> + 0 },
> + /* Force channel A/B/C/D QBias on */
> + { LAN8814_PAGE_POWER_REGS,
> + LAN9645X_BTRX_QBIAS_POWER_DOWN,
> + 0xaa },
> + /* tx low I on channel C/D overwrite */
> + { LAN8814_PAGE_POWER_REGS,
> + LAN9645X_TX_LOW_I_CH_CD_POWER_MGMT,
> + 0xbfff },
> + /* channel B low I overwrite */
> + { LAN8814_PAGE_POWER_REGS,
> + LAN9645X_TX_LOW_I_CH_B_POWER_MGMT,
> + 0xabbf },
> + /* channel A low I overwrite */
> + { LAN8814_PAGE_POWER_REGS,
> + LAN9645X_TX_LOW_I_CH_A_POWER_MGMT,
> + 0xbd3f },
> +};
It looks like this erratum not publicly documented. At least not here:
https://ww1.microchip.com/downloads/aemDocuments/documents/UNG/ProductDocuments/Errata/LAN9645xS-LAN9645xF-Errata-DS80001187.pdf
re there more information about it? Can it be described in the comment?
> +
> +static int lan9645x_config_init(struct phy_device *phydev)
> +{
> + int ret;
> +
> + /* Apply erratas. */
> + ret = lan8842_erratas(phydev);
> + if (ret < 0)
> + return ret;
> +
> + return lanphy_write_reg_data(phydev, force_dac_tx_errata,
> + ARRAY_SIZE(force_dac_tx_errata));
> +}
> +
> +static int lan9645x_suspend(struct phy_device *phydev)
> +{
> + int aneg_en_state, ret;
> +
> + /* Software workaround from design to handle SPD. SPD will stop AFE
> + * clock from AFE port, which makes the system MAC fifo unable to flush.
> + * The workaround is to restart ANEG and wait for flush, before issuing
> + * software power down.
> + */
> + aneg_en_state = phy_read(phydev, MII_BMCR) & BMCR_ANENABLE;
> +
> + ret = phy_restart_aneg(phydev);
> + if (ret)
> + return ret;
> +
> + /* Allow time for system FIFO flush data */
> + usleep_range(8 * USEC_PER_MSEC, 12 * USEC_PER_MSEC);
MAC and PHY power management are not always fully coupled (implementation
specific), are there other ways to sync them with each other, except of
unconditional sleep in the PHY driver. I expect that someone making
changes on the MAC driver may miss this nuance.
Best Regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2026-01-23 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 7:50 [PATCH net-next] net: phy: micrel: Add support for lan9645x internal phy Jens Emil Schulz Østergaard
2026-01-23 8:57 ` Maxime Chevallier
2026-01-23 13:40 ` Jens Emil Schulz Ostergaard
2026-01-23 9:55 ` Oleksij Rempel [this message]
2026-01-23 15:12 ` Jens Emil Schulz Ostergaard
2026-01-23 16:11 ` Andrew Lunn
2026-01-27 8:49 ` Jens Emil Schulz Ostergaard
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=aXNFrDOdPanZ_cjk@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=Steen.Hegelund@microchip.com \
--cc=andrew@lunn.ch \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=jensemil.schulzostergaard@microchip.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rsc@pengutronix.de \
/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