From: Kyle Hendry <kylehendrydev@gmail.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>,
Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: noltari@gmail.com, jonas.gorski@gmail.com,
Kyle Hendry <kylehendrydev@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH RESEND net-next 0/2] net: dsa: b53: mmap: Add bcm63268 GPHY power control
Date: Wed, 13 Aug 2025 17:25:26 -0700 [thread overview]
Message-ID: <20250814002530.5866-1-kylehendrydev@gmail.com> (raw)
The gpio controller on the bcm63268 has a register for
controlling the gigabit phy power. These patches disable
low power mode when enabling the gphy port.
This is based on an earlier patch series here:
https://lore.kernel.org/netdev/20250306053105.41677-1-kylehendrydev@gmail.com/
I have created a new series since many of the changes
were included in the ephy control patches:
https://lore.kernel.org/netdev/20250724035300.20497-1-kylehendrydev@gmail.com/
Signed-off-by: Kyle Hendry <kylehendrydev@gmail.com>
Kyle Hendry (2):
net: dsa: b53: mmap: Add gphy port to phy info for bcm63268
net: dsa: b53: mmap: Implement bcm63268 gphy power control
drivers/net/dsa/b53/b53_mmap.c | 35 ++++++++++++++++++++++++++++++----
1 file changed, 31 insertions(+), 4 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-14 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 0:25 Kyle Hendry [this message]
2025-08-14 0:25 ` [PATCH RESEND net-next 1/2] net: dsa: b53: mmap: Add gphy port to phy info for bcm63268 Kyle Hendry
2025-08-14 0:25 ` [PATCH RESEND net-next 2/2] net: dsa: b53: mmap: Implement bcm63268 gphy power control Kyle Hendry
2025-08-15 1:30 ` [PATCH RESEND net-next 0/2] net: dsa: b53: mmap: Add bcm63268 GPHY " patchwork-bot+netdevbpf
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=20250814002530.5866-1-kylehendrydev@gmail.com \
--to=kylehendrydev@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=jonas.gorski@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noltari@gmail.com \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
/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).