From: Andrew Lunn <andrew@lunn.ch>
To: "Kamil Horák (2N)" <kamilh@axis.com>
Cc: florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, krzk+dt@kernel.org,
conor+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
robh@kernel.org
Subject: Re: [PATCH 2/3] net: phy: bcm5481x: Implement MII-Lite mode
Date: Fri, 20 Jun 2025 17:19:59 +0200 [thread overview]
Message-ID: <f8662437-58ea-4ae5-8fbc-eb06e22f5a1c@lunn.ch> (raw)
In-Reply-To: <20250620134430.1849344-2-kamilh@axis.com>
On Fri, Jun 20, 2025 at 03:44:28PM +0200, Kamil Horák (2N) wrote:
> 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.
Please could you say more about what mii-lite is. Rather than adding a
bool DT property, i'm asking myself should we add interface mode for
it?
Is it a mode of its own? MII normally means Fast Ethernet, 100Mbps. Is
that what MII-Lite supports? How does it differ from RMII? Should we
be calling this PHY_INTERFACE_MODE_LMII?
Andrew
next prev parent reply other threads:[~2025-06-20 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 13:44 [PATCH 0/3] net: phy: bcm54811: Fix the PHY initialization Kamil Horák (2N)
2025-06-20 13:44 ` [PATCH 2/3] net: phy: bcm5481x: Implement MII-Lite mode Kamil Horák (2N)
2025-06-20 15:19 ` Andrew Lunn [this message]
2025-06-20 13:44 ` [PATCH 1/3] net: phy: bcm54811: Fix the PHY initialization Kamil Horák (2N)
2025-06-20 13:44 ` [PATCH 3/3] dt-bindings: ethernet-phy: add optional mii-lite-mode flag Kamil Horák (2N)
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=f8662437-58ea-4ae5-8fbc-eb06e22f5a1c@lunn.ch \
--to=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=kamilh@axis.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=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 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®