From: "Rob Herring (Arm)" <robh@kernel.org>
To: "Kamil Horák - 2N" <kamilh@axis.com>
Cc: linux@armlinux.org.uk, corbet@lwn.net, linux-doc@vger.kernel.org,
krzk+dt@kernel.org, bcm-kernel-feedback-list@broadcom.com,
florian.fainelli@broadcom.com, hkallweit1@gmail.com,
pabeni@redhat.com, kuba@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, conor+dt@kernel.org,
netdev@vger.kernel.org, andrew+netdev@lunn.ch, horms@kernel.org,
davem@davemloft.net, edumazet@google.com,
Maxime Chevallier <maxime.chevallier@bootlin.com>,
andrew@lunn.ch
Subject: Re: [PATCH net-next v7 2/4] dt-bindings: ethernet-phy: add MII-Lite phy interface type
Date: Tue, 8 Jul 2025 16:15:39 -0500 [thread overview]
Message-ID: <175200933841.1032309.15245293992929519207.robh@kernel.org> (raw)
In-Reply-To: <20250708090140.61355-3-kamilh@axis.com>
On Tue, 08 Jul 2025 11:01:38 +0200, Kamil Horák - 2N wrote:
> Some Broadcom PHYs are capable to operate in simplified MII mode,
> without TXER, RXER, CRS and COL signals as defined for the MII.
> The MII-Lite mode can be used on most Ethernet controllers with full
> MII interface by just leaving the input signals (RXER, CRS, COL)
> inactive. 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 all full-duplex only.
>
> Add new interface type "mii-lite" to phy-connection-type enum.
>
> Signed-off-by: Kamil Horák - 2N <kamilh@axis.com>
> Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
> ---
> Documentation/devicetree/bindings/net/ethernet-controller.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2025-07-08 21:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 9:01 [PATCH net-next v7 0/4] net: phy: bcm54811: PHY initialization Kamil Horák - 2N
2025-07-08 9:01 ` [PATCH net-next v7 1/4] net: phy: MII-Lite PHY interface mode Kamil Horák - 2N
2025-07-08 9:03 ` Russell King (Oracle)
2025-07-08 9:01 ` [PATCH net-next v7 2/4] dt-bindings: ethernet-phy: add MII-Lite phy interface type Kamil Horák - 2N
2025-07-08 21:15 ` Rob Herring (Arm) [this message]
2025-07-08 9:01 ` [PATCH net-next v7 3/4] net: phy: bcm5481x: MII-Lite activation Kamil Horák - 2N
2025-07-08 9:04 ` Russell King (Oracle)
2025-07-08 9:01 ` [PATCH net-next v7 4/4] net: phy: bcm54811: PHY initialization Kamil Horák - 2N
2025-07-10 3:00 ` [PATCH net-next v7 0/4] " patchwork-bot+netdevbpf
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=175200933841.1032309.15245293992929519207.robh@kernel.org \
--to=robh@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kamilh@axis.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.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
all inboxes | Powered by JetHome®