Hi Kamil,

On Mon, 23 Jun 2025 17:10:46 +0200
Kamil Horák - 2N [off-list ref] wrote:

From: Kamil Horák (2N) <redacted>

The Broadcom bcm54810 and bcm54811 PHYs are capable to operate in
simplified MII mode, without TXER, RXER, CRS and COL signals as defined
for the MII. While the PHY can be strapped for MII mode, the selection
between MII and MII-Lite must be done by software.
The MII-Lite mode can be used with some Ethernet controllers, usually
those used in automotive applications. The absence of COL signal
makes half-duplex link modes impossible but does not interfere with
BroadR-Reach link modes on Broadcom PHYs, because they are full-duplex
only. The MII-Lite mode can be also used on an Ethernet controller with
full MII interface by just leaving the input signals (RXER, CRS, COL)
inactive.

I'm following-up to Andrew's suggestion of making it a dedicated
phy-mode. You say that this requires only phy-side configuration,
however you also say that with MII-lite, you can't do half-duplex.

Looking at the way we configure the MAC to PHY link, how can the MAC
driver know that HD isn't available if this is a phy-only property ?

Relying on the fact that the PHYs that use MII-Lite will only ever
setup a full-duplex link with the partner seems a bit fragile, when we
could indicate that this new MII-Lite mode only supports 10FD/100FD,
through this mapping code here :

https://elixir.bootlin.com/linux/v6.16-rc2/source/drivers/net/phy/phy_caps.c#L282

Besides that, given that this is a physically different MAC to PHY
interface (missing signals compared to MII), one could also argue that
this warrants a dedicated phy-mode.

Maxime