From: Nicolai Buchwitz <nb@tipi-net.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Thangaraj Samynathan <thangaraj.s@microchip.com>,
netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, bryan.whitehead@microchip.com,
UNGLinuxDriver@microchip.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 2/2] net: lan743x: add support for RMII interface
Date: Wed, 27 May 2026 14:38:38 +0200 [thread overview]
Message-ID: <c0c65d225270c91323bdc7f790d9356b@tipi-net.de> (raw)
In-Reply-To: <e66d0929-6fa1-415c-80fe-d2635bf74e19@lunn.ch>
On 27.5.2026 14:20, Andrew Lunn wrote:
> [...]
>> ksz_common is exactly that: it puts RMII in lpi_interfaces on purpose
>> and uses a dummy mac_enable_tx_lpi() (the comment there explains the
>> HW
>> handles LPI itself once EEE is negotiated):
> [...]
>
> and this is a 3rd variant, were you have an MAC/PHY pair which is
> tightly integrated. I doubt that RMII is actually being used, and the
> phy_interface_t should actually by "internal".
So, if we treat this as a special case, patch it and track LPI
internally ...
>
>> So clearing RMII in phylink would break EEE there.
>
> Agreed. So maybe it is too late to do this in the core, at least not
> without having to change some drivers.
... we could clear the bits in phylink when RMII is used? Arguably this
patch is the first occurrence of such a construct, but who knows what
the future will bring... Better be explicit in the framework than
rework it later?
> Andrew
Nicolai
next prev parent reply other threads:[~2026-05-27 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 15:40 [PATCH net-next v2 0/2] net: lan743x: add RMII support for PCI11x1x Thangaraj Samynathan
2026-05-26 15:40 ` [PATCH net-next v2 1/2] net: lan743x: add RMII strap status detection " Thangaraj Samynathan
2026-05-26 16:40 ` Andrew Lunn
2026-05-27 3:21 ` Thangaraj.S
2026-05-27 12:12 ` Andrew Lunn
2026-05-26 15:40 ` [PATCH net-next v2 2/2] net: lan743x: add support for RMII interface Thangaraj Samynathan
2026-05-26 16:49 ` Andrew Lunn
2026-05-26 19:59 ` Nicolai Buchwitz
2026-05-27 10:11 ` Nicolai Buchwitz
2026-05-27 12:20 ` Andrew Lunn
2026-05-27 12:38 ` Nicolai Buchwitz [this message]
2026-05-27 3:23 ` Thangaraj.S
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=c0c65d225270c91323bdc7f790d9356b@tipi-net.de \
--to=nb@tipi-net.de \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=bryan.whitehead@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thangaraj.s@microchip.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
all inboxes | Powered by JetHome®