From: Andrew Lunn <andrew@lunn.ch>
To: Piyush Malgujar <pmalgujar@marvell.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chandrakala Chavva <cchavva@marvell.com>,
Damian Eppel <deppel@marvell.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH] Marvell MDIO clock related changes.
Date: Fri, 29 Apr 2022 16:24:53 +0200 [thread overview]
Message-ID: <Ymv1NU6hvCpAo5+F@lunn.ch> (raw)
In-Reply-To: <CH0PR18MB4193CF9786F80101D08A2431A3FC9@CH0PR18MB4193.namprd18.prod.outlook.com>
> > > 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
next prev parent reply other threads:[~2022-04-29 14:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 14:14 [PATCH] Marvell MDIO clock related changes Piyush Malgujar
2022-04-29 14:24 ` Andrew Lunn [this message]
2022-05-26 10:57 ` Piyush Malgujar
2022-05-26 21:46 ` Andrew Lunn
-- strict thread matches above, loose matches on Subject: below --
2022-04-15 14:30 Piyush Malgujar
2022-04-15 15:05 ` Andrew Lunn
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=Ymv1NU6hvCpAo5+F@lunn.ch \
--to=andrew@lunn.ch \
--cc=cchavva@marvell.com \
--cc=davem@davemloft.net \
--cc=deppel@marvell.com \
--cc=hkallweit1@gmail.com \
--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=pmalgujar@marvell.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;
as well as URLs for NNTP newsgroup(s).