Re: [PATCH net-next v2 3/3] dt-bindings: ethernet-phy: add optional mii-lite-mode flag
From: Russell King (Oracle)
Date: Mon Jun 23 2025 - 12:05:09 EST
On Mon, Jun 23, 2025 at 05:10:48PM +0200, Kamil Horák - 2N wrote:
> From: Kamil Horák (2N) <kamilh@xxxxxxxx>
>
> The Broadcom bcm54810 and bcm54811 PHYs support MII and MII-Lite
> interface modes. The MII-Lite mode does not use TXR, RXER, CRS and COL
> signals. However, the hardware strapping only selects MII mode,
> distinction between MII and MII-Lite must be done by software.
>
> Add optional mii-lite-mode flag to switch the PHY to MII-Lite mode.
>
> Signed-off-by: Kamil Horák (2N) <kamilh@xxxxxxxx>
> ---
> Documentation/devicetree/bindings/net/ethernet-phy.yaml | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> index 71e2cd32580f..edfd16044770 100644
> --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml
> @@ -101,6 +101,14 @@ properties:
> 1BR-10 names. The PHY must be configured to operate in BroadR-Reach mode
> by software.
>
> + mii-lite-mode:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description:
> + If set, indicates the use of MII-Lite variant of MII, without the
> + functions of TXER, RXER, CRS and COL signals for Broadcom PHYs. These
> + PHYs can be strapped to use MII mode but the MII or MII-Lite selection
> + must be done by software.
I'll put the same question here as I did on patch 2. Do we want this to
be a separate property, or would it make more sense as a different
phy-mode value?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!