[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Ymv1NU6hvCpAo5+F@lunn.ch>
Date: Fri, 29 Apr 2022 16:24:53 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Piyush Malgujar <pmalgujar@...vell.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Chandrakala Chavva <cchavva@...vell.com>,
Damian Eppel <deppel@...vell.com>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH] Marvell MDIO clock related changes.
> > > 2) Marvell MDIO clock frequency attribute change:
> > > This MDIO change provides an option for user to have the bus speed set
> > > to their needs which is otherwise set to default(3.125 MHz).
> >
> > Please read 802.3 Clause 22. The default should be 2.5MHz.
> >
>
> These changes are only specific to Marvell Octeon family.
Are you saying the Marvell Octeon family decide to ignore 802.3? Have
you tested every possible PHY that could be connected to this MDIO bus
and they all work for 3.125MHz, even though 802.3 says they only need
to support up to 2.5Mhz?
Andrew
Powered by blists - more mailing lists