From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Golle <daniel@makrotopia.org>
Cc: Xu Liang <lxu@maxlinear.com>,
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>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 3/3] net: phy: mxl-86110: add basic support for MxL86111 PHY
Date: Wed, 20 Aug 2025 14:40:26 +0200 [thread overview]
Message-ID: <2bcbb7e6-c085-46ce-a3db-136263c30543@lunn.ch> (raw)
In-Reply-To: <eb4e42e02a729a084e2f995c29a08893ac24593e.1755691622.git.daniel@makrotopia.org>
On Wed, Aug 20, 2025 at 01:12:06PM +0100, Daniel Golle wrote:
> Add basic support for the MxL86111 PHY which in addition to the features
> of the MxL86110 also comes with an SGMII interface.
> Setup the interface mode and take care of in-band-an.
>
> Currently only RGMII-to-UTP and SGMII-to-UTP modes are supported while the
> PHY would also support RGMII-to-1000Base-X, including automatic selection
> of the Fiber or UTP link depending on the presence of a link partner.
>
> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2025-08-20 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 12:11 [PATCH net-next v3 1/3] net: phy: mxl-86110: add basic support for led_brightness_set op Daniel Golle
2025-08-20 12:11 ` [PATCH net-next v3 2/3] net: phy: mxl-86110: fix indentation in struct phy_driver Daniel Golle
2025-08-20 12:36 ` Andrew Lunn
2025-08-20 12:12 ` [PATCH net-next v3 3/3] net: phy: mxl-86110: add basic support for MxL86111 PHY Daniel Golle
2025-08-20 12:40 ` Andrew Lunn [this message]
2025-08-20 12:34 ` [PATCH net-next v3 1/3] net: phy: mxl-86110: add basic support for led_brightness_set op Andrew Lunn
2025-08-20 13:34 ` Daniel Golle
2025-08-22 0:36 ` Jakub Kicinski
2025-08-22 2:06 ` Daniel Golle
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=2bcbb7e6-c085-46ce-a3db-136263c30543@lunn.ch \
--to=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lxu@maxlinear.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).