lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: 
 <175211642700.969691.12423732626621793373.git-patchwork-notify@kernel.org>
Date: Thu, 10 Jul 2025 03:00:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Kamil HorĂ¡k - 2N <kamilh@...s.com>@codeaurora.org
Cc: florian.fainelli@...adcom.com, bcm-kernel-feedback-list@...adcom.com,
 andrew@...n.ch, hkallweit1@...il.com, linux@...linux.org.uk,
 davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 krzk+dt@...nel.org, conor+dt@...nel.org, netdev@...r.kernel.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, robh@...nel.org,
 andrew+netdev@...n.ch, horms@...nel.org, corbet@....net,
 linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next v7 0/4] net: phy: bcm54811: PHY initialization

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.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



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ