From: "Kamil Horák (2N)" <kamilh@axis.com>
To: <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>
Cc: <kamilh@axis.com>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<robh@kernel.org>
Subject: [PATCH 0/3] net: phy: bcm54811: Fix the PHY initialization
Date: Fri, 20 Jun 2025 15:44:27 +0200 [thread overview]
Message-ID: <20250620134430.1849344-1-kamilh@axis.com> (raw)
PATCH 1 - 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.
PATCH 2 - Fix the BCM54811 PHY initialization by implementing MII-Lite
mode switch
PATCH 3 - Add optional mii-lite-mode flag to switch the PHY to MII-Lite
Kamil Horák (2N) (3):
net: phy: bcm54811: Fix the PHY initialization
net: phy: bcm5481x: Implement MII-Lite mode
dt-bindings: ethernet-phy: add optional mii-lite-mode flag
.../devicetree/bindings/net/ethernet-phy.yaml | 8 +++
drivers/net/phy/broadcom.c | 54 +++++++++++++++++--
include/linux/brcmphy.h | 7 +++
3 files changed, 66 insertions(+), 3 deletions(-)
--
2.39.5
next reply other threads:[~2025-06-20 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 13:44 Kamil Horák (2N) [this message]
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
2025-06-23 8:17 ` Kamil Horák (2N)
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=20250620134430.1849344-1-kamilh@axis.com \
--to=kamilh@axis.com \
--cc=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=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;
as well as URLs for NNTP newsgroup(s).