From: Kyle Hendry <kylehendrydev@gmail.com>
To: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Philipp Zabel <p.zabel@pengutronix.de>
Cc: noltari@gmail.com, jonas.gorski@gmail.com,
Kyle Hendry <kylehendrydev@gmail.com>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/3] net: phy: bcm63xx: add support for BCM63268 GPHY
Date: Thu, 27 Feb 2025 16:27:14 -0800 [thread overview]
Message-ID: <20250228002722.5619-1-kylehendrydev@gmail.com> (raw)
Some BCM63268 bootloaders do not enable the internal PHYs by default.
This patch series adds a phy driver to set the registers required
for the gigabit PHY to work.
v3 changes:
- Remove syscon for the GPHY control register
- Change driver to access the GPIO controller syscon
- Move syscon phandle from mdio bus to phy node
- Remove unecessary devm_phy_package_join()
- Made functions static to fix build warning
- Fix formatting and whitespace issues
- Add schema for PHY driver
- Deassert PHY reset signal
v2: https://lore.kernel.org/netdev/d819144d-ce2f-4ea5-8bfb-83e341672da6@gmail.com/
- Remove changes to b53 dsa code and rework fix as a PHY driver
- Use a regmap for accessing GPHY control register
- Add documentaion for device tree changes
v1: https://lore.kernel.org/netdev/20250206043055.177004-1-kylehendrydev@gmail.com/
Signed-off-by: Kyle Hendry <kylehendrydev@gmail.com>
Kyle Hendry (3):
net: phy: bcm63xx: add support for BCM63268 GPHY
net: phy: enable bcm63xx on bmips
dt-bindings: net: phy: add BCM63268 GPHY
.../bindings/net/brcm,bcm63268-gphy.yaml | 51 +++++++++
drivers/net/phy/Kconfig | 4 +-
drivers/net/phy/bcm63xx.c | 101 ++++++++++++++++++
3 files changed, 154 insertions(+), 2 deletions(-)
create mode 100644 Documentation/devicetree/bindings/net/brcm,bcm63268-gphy.yaml
--
2.43.0
next reply other threads:[~2025-02-28 0:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 0:27 Kyle Hendry [this message]
2025-02-28 0:27 ` [PATCH v3 1/3] net: phy: bcm63xx: add support for BCM63268 GPHY Kyle Hendry
2025-02-28 9:34 ` Kory Maincent
2025-02-28 0:27 ` [PATCH v3 2/3] net: phy: enable bcm63xx on bmips Kyle Hendry
2025-02-28 0:27 ` [PATCH v3 3/3] dt-bindings: net: phy: add BCM63268 GPHY Kyle Hendry
2025-02-28 1:25 ` Rob Herring (Arm)
2025-02-28 9:25 ` [PATCH v3 0/3] net: phy: bcm63xx: add support for " Kory Maincent
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=20250228002722.5619-1-kylehendrydev@gmail.com \
--to=kylehendrydev@gmail.com \
--cc=andrew+netdev@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=jonas.gorski@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=noltari@gmail.com \
--cc=p.zabel@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.