From: Christian Marangi <ansuelsmth@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Philipp Zabel <p.zabel@pengutronix.de>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next RFC PATCH 2/2] net: mdio: Add MDIO bus controller for Airoha AN7583
Date: Wed, 28 May 2025 00:39:45 +0200 [thread overview]
Message-ID: <68363f34.050a0220.351f97.06f7@mx.google.com> (raw)
In-Reply-To: <e289d26e-9453-45f5-bfa6-f53f9e4647af@lunn.ch>
On Wed, May 28, 2025 at 12:36:46AM +0200, Andrew Lunn wrote:
> > +#define AN7583_MDIO_PHY 0xd4
> > +#define AN7583_MDIO1_SPEED_MODE BIT(11)
> > +#define AN7583_MDIO0_SPEED_MODE BIT(10)
>
> Is there any documentation about what these bits do? The bus should
> default to 2.5Mhz.
>
No but I can ask. In theory tho these MDIO controller are used for 10g
or 2.5g PHY that all require a firmware to load so 2.5MHz makes the boot
time of 2+ minute.
The documentation say...
1: fast mode
0: normal mode
Very useful I guess :D
--
Ansuel
next prev parent reply other threads:[~2025-05-27 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 21:34 [net-next RFC PATCH 1/2] dt-bindings: net: Document support for Airoha AN7583 MDIO Controller Christian Marangi
2025-05-27 21:34 ` [net-next RFC PATCH 2/2] net: mdio: Add MDIO bus controller for Airoha AN7583 Christian Marangi
2025-05-27 22:36 ` Andrew Lunn
2025-05-27 22:39 ` Christian Marangi [this message]
2025-05-27 23:18 ` Andrew Lunn
2025-06-05 19:52 ` [net-next RFC PATCH 1/2] dt-bindings: net: Document support for Airoha AN7583 MDIO Controller Rob Herring
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=68363f34.050a0220.351f97.06f7@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pabeni@redhat.com \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.