From: Jens Emil Schulz Ostergaard <jensemil.schulzostergaard@microchip.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: 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>,
<o.rempel@pengutronix.de>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Daniel Machon <daniel.machon@microchip.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2] net: phy: micrel: Add support for lan9645x internal phy
Date: Wed, 25 Feb 2026 21:57:35 +0100 [thread overview]
Message-ID: <eb0f7899f25721bf3b29475aec65018584600321.camel@microchip.com> (raw)
In-Reply-To: <42918203-276e-42a9-a9da-34d43a5e6a98@lunn.ch>
On Wed, 2026-02-25 at 14:39 +0100, Andrew Lunn wrote:
>
> > > > > > > +static int lan9645x_suspend(struct phy_device *phydev)
> > > > > > > +{
> > > > > > > + int ret, val;
> > > > > > > +
> > > > > > > + /* Force link down before software power down (SPD), by doing software
> > > > > > > + * soft reset. This resets the PHY, but keeps all register configuration
> > > > > > > + * intact. The bit self clears.
> > > > > > > + *
> > > > > > > + * This is needed as a workaround for an issue where performing SPD on a
> > > > > > > + * port can bring adjacent ports down, when there is traffic flowing
> > > > > > > + * through the ports.
> > > > > > > + */
> > > > > > > + ret = phy_modify(phydev, LAN9645X_CONTROL_REGISTER,
> > > > > > > + LAN9645X_CONTROL_REGISTER_SOFT_RESET, 1);
> > > > >
> > > > > Any specific reason why you use a vendor-specific register here instead of BMCR
> > > > > via genphy_soft_reset()?
> > > > >
> > > > >
> > > >
> > > > Sorry I missed your mail. genphy_soft_reset() will do a software (hard) reset via
> > > > bit 15 (BMCR_RESET). In particular it will reset the registers. We want to do
> > > > a software soft reset, which resets the PHY without changing register values.
> > > >
> > > No, BMCR_RESET usually doesn't reset configuration registers. That's why the
> > > function is called genphy_*soft*_reset. In case your PHY behaves different,
> > > which configuration registers does it change?
> > >
> >
> > Ok I tought that was the usual behavior. The register spec says BMCR_RESET will reset
> > the PHY and all its registers to their default state.
>
> Most PHYs do a soft reset when this bit is set, but some do a much
> harder reset, resetting all state including registers.
>
> Does the documentation say anything about
> LAN9645X_CONTROL_REGISTER_SOFT_RESET and self clearing? BMCR_RESET
> should be cleared by the PHY when the reset is
> complete. genphy_soft_reset() uses phy_poll_reset() to wait for the
> bit to clear. If you don't wait, it could be your start writing to
> registers while the reset is still happening, and those writes get
> lost. You might have the same issue here.
>
> Andrew
Yes, it says the bit is self-clearing (R/W1S/SC). In the next version I
am currently setting the bit with phy_set_bits, and then poll for the bit
to clear with phy_read_poll_timeout.
Thanks,
Emil
prev parent reply other threads:[~2026-02-25 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 9:12 [PATCH net-next v2] net: phy: micrel: Add support for lan9645x internal phy Jens Emil Schulz Østergaard
2026-01-31 6:29 ` Jens Emil Schulz Ostergaard
2026-01-31 10:00 ` Heiner Kallweit
2026-02-20 20:38 ` Jens Emil Schulz Ostergaard
2026-02-20 20:50 ` Heiner Kallweit
2026-02-20 21:10 ` Russell King (Oracle)
2026-02-20 21:22 ` Andrew Lunn
2026-02-20 21:30 ` Heiner Kallweit
2026-02-20 21:49 ` Russell King (Oracle)
2026-02-25 12:35 ` Jens Emil Schulz Ostergaard
2026-02-25 13:39 ` Andrew Lunn
2026-02-25 20:57 ` Jens Emil Schulz Ostergaard [this message]
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=eb0f7899f25721bf3b29475aec65018584600321.camel@microchip.com \
--to=jensemil.schulzostergaard@microchip.com \
--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=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.com \
/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