From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Kamil_Hor=C3=A1k_-_2N_=3Ckamilh=40axis=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: florian.fainelli@broadcom.com,
bcm-kernel-feedback-list@broadcom.com, andrew@lunn.ch,
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, andrew+netdev@lunn.ch, horms@kernel.org,
corbet@lwn.net, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v7 0/4] net: phy: bcm54811: PHY initialization
Date: Thu, 10 Jul 2025 03:00:27 +0000 [thread overview]
Message-ID: <175211642700.969691.12423732626621793373.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250708090140.61355-1-kamilh@axis.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 8 Jul 2025 11:01:36 +0200 you wrote:
> Proper bcm54811 PHY driver initialization for MII-Lite.
>
> The bcm54811 PHY in MLP package must be setup for MII-Lite interface
> mode by software. Normally, the PHY to MAC interface is selected in
> hardware by setting the bootstrap pins of the PHY. However, MII and
> MII-Lite share the same hardware setup and must be distinguished by
> software, setting appropriate bit in a configuration register.
> The MII-Lite interface mode is non-standard one, defined by Broadcom
> for some of their PHYs. The MII-Lite lightness consist in omitting
> RXER, TXER, CRS and COL signals of the standard MII interface.
> Absence of COL them makes half-duplex links modes impossible but
> does not interfere with Broadcom's BroadR-Reach link modes, because
> they are full-duplex only.
> To do it in a clean way, MII-Lite must be introduced first, including
> its limitation to link modes (no half-duplex), because it is a
> prerequisite for the patch #3 of this series. The patch #4 does not
> depend on MII-Lite directly but both #3 and #4 are necessary for
> bcm54811 to work properly without additional configuration steps to be
> done - for example in the bootloader, before the kernel starts.
>
> [...]
Here is the summary with links:
- [net-next,v7,1/4] net: phy: MII-Lite PHY interface mode
https://git.kernel.org/netdev/net-next/c/67c0170566b5
- [net-next,v7,2/4] dt-bindings: ethernet-phy: add MII-Lite phy interface type
https://git.kernel.org/netdev/net-next/c/fbe937473f3a
- [net-next,v7,3/4] net: phy: bcm5481x: MII-Lite activation
https://git.kernel.org/netdev/net-next/c/34bf222824f6
- [net-next,v7,4/4] net: phy: bcm54811: PHY initialization
https://git.kernel.org/netdev/net-next/c/3117a11fff5a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-07-10 3:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 9:01 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)
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 ` patchwork-bot+netdevbpf [this message]
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=175211642700.969691.12423732626621793373.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Kamil_Hor=C3=A1k_-_2N_=3Ckamilh=40axis=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.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=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=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®