netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
	ezra@synergy-village.org, Tristram Ha <Tristram.Ha@microchip.com>,
	Michael Walle <michael@walle.cc>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net] net: mdio: Prevent Clause 45 scan on SMSC PHYs
Date: Tue, 2 Jan 2024 14:00:03 +0000	[thread overview]
Message-ID: <ZZQW40bXteaiWDOZ@shell.armlinux.org.uk> (raw)
In-Reply-To: <1297166c-38c1-4041-8a7f-403477b871cf@lunn.ch>

On Tue, Jan 02, 2024 at 02:42:17PM +0100, Andrew Lunn wrote:
> On Mon, Jan 01, 2024 at 11:44:38PM +0100, Heiner Kallweit wrote:
> > On 01.01.2024 22:31, Ezra Buehler wrote:
> > > Since commit 1a136ca2e089 ("net: mdio: scan bus based on bus
> > > capabilities for C22 and C45") our AT91SAM9G25-based GARDENA smart
> > > Gateway will no longer boot.
> > > 
> > > Prior to the mentioned change, probe_capabilities would be set to
> > > MDIOBUS_NO_CAP (0) and therefore, no Clause 45 scan was performed.
> > > Running a Clause 45 scan on an SMSC/Microchip LAN8720A PHY will (at
> > > least with our setup) considerably slow down kernel startup and
> > > ultimately result in a board reset.
> > > 
> > > AFAICT all SMSC/Microchip PHYs are Clause 22 devices. Some have a
> > > "Clause 45 protection" feature (e.g. LAN8830) and others like the
> > > LAN8804 will explicitly state the following in the datasheet:
> > > 
> > >     This device may respond to Clause 45 accesses and so must not be
> > >     mixed with Clause 45 devices on the same MDIO bus.
> > > 
> > 
> > I'm not convinced that some heuristic based on vendors is a
> > sustainable approach. Also I'd like to avoid (as far as possible)
> > that core code includes vendor driver headers. Maybe we could use
> > a new PHY driver flag. Approaches I could think of:
> 
> We already have a core hack for these broken PHYs:

Yes, and it is this very function that the patch at the start of this
thread is changing!

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2024-01-02 14:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 21:31 [PATCH net] net: mdio: Prevent Clause 45 scan on SMSC PHYs Ezra Buehler
2024-01-01 22:44 ` Heiner Kallweit
2024-01-02  8:50   ` Michael Walle
2024-01-02  9:14     ` Heiner Kallweit
2024-01-02 12:02   ` Russell King (Oracle)
2024-01-02 13:42   ` Andrew Lunn
2024-01-02 14:00     ` Russell King (Oracle) [this message]
2024-01-02 14:04     ` Ezra Buehler
2024-01-02 14:06     ` Heiner Kallweit
2024-01-02 15:50       ` Andrew Lunn
2024-01-02 18:08         ` Ezra Buehler
2024-01-02 18:57           ` Russell King (Oracle)
2024-01-06 12:41             ` Ezra Buehler
2024-01-06 15:20               ` Andrew Lunn
2024-01-07 13:51                 ` Ezra Buehler
2024-01-02 19:49           ` Andrew Lunn
2024-01-02 20:05             ` Ezra Buehler

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=ZZQW40bXteaiWDOZ@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=Tristram.Ha@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=ezra@synergy-village.org \
    --cc=hkallweit1@gmail.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=michael@walle.cc \
    --cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).