linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: "Kamil Horák - 2N" <kamilh@axis.com>, florian.fainelli@broadcom.com
Cc: <bcm-kernel-feedback-list@broadcom.com>, <andrew@lunn.ch>,
	<hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
	<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
	<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
	<netdev@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <f.fainelli@gmail.com>,
	<robh@kernel.org>, <andrew+netdev@lunn.ch>, <horms@kernel.org>,
	<corbet@lwn.net>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH net v5 0/4] net: phy: bcm54811: Fix the PHY initialization
Date: Wed, 2 Jul 2025 15:02:16 -0700	[thread overview]
Message-ID: <20250702150216.2a5410b3@kernel.org> (raw)
In-Reply-To: <20250701075015.2601518-1-kamilh@axis.com>

On Tue, 1 Jul 2025 09:50:11 +0200 Kamil Horák - 2N wrote:
> PATCH 1 - Add MII-Lite PHY interface mode as defined by Broadcom for
>    their two-wire PHYs. It can be used with most Ethernet controllers
>    under certain limitations (no half-duplex link modes etc.).
> 
> PATCH 2 - Add MII-Lite PHY interface type
> 
> PATCH 3 - Activation of MII-Lite interface mode on Broadcom bcm5481x
>    PHYs
> 
> PATCH 4 - Fix the BCM54811 PHY initialization so that it conforms
>    to the datasheet regarding a reserved bit in the LRE Control
>    register, which must be written to zero after every device reset.
>    Also fix the LRE Status register reading, there is another bit to
>    be ignored on bcm54811.

I'm a bit lost why the first 3 patches are included in a series for net.
My naive reading is we didn't support this extra mode, now we do,
which sounds like a new feature.. Patch 4, sure, but the dependency
is not obvious.

  parent reply	other threads:[~2025-07-02 22:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01  7:50 [PATCH net v5 0/4] net: phy: bcm54811: Fix the PHY initialization Kamil Horák - 2N
2025-07-01  7:50 ` [PATCH net v5 1/4] net: phy: MII-Lite PHY interface mode Kamil Horák - 2N
2025-07-01  7:50 ` [PATCH net v5 2/4] dt-bindings: ethernet-phy: add MII-Lite phy interface type Kamil Horák - 2N
2025-07-01  7:50 ` [PATCH net v5 3/4] net: phy: bcm5481x: MII-Lite activation Kamil Horák - 2N
2025-07-01  7:50 ` [PATCH net v5 4/4] net: phy: bcm54811: Fix the PHY initialization Kamil Horák - 2N
2025-07-02 22:02 ` Jakub Kicinski [this message]
2025-07-02 23:46   ` [PATCH net v5 0/4] " Florian Fainelli
2025-07-03  9:03     ` Kamil Horák (2N)
2025-07-03 10:03       ` Paolo Abeni
2025-07-04  8:35         ` 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=20250702150216.2a5410b3@kernel.org \
    --to=kuba@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=f.fainelli@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=kamilh@axis.com \
    --cc=krzk+dt@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;
as well as URLs for NNTP newsgroup(s).