From: patchwork-bot+netdevbpf@kernel.org
To: A. Sverdlin <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, daniel@makrotopia.org, hauke@hauke-m.de,
andrew@lunn.ch, olteanv@gmail.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
linux@armlinux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5] net: dsa: mxl-gsw1xx: force internal PHYs into a known reset state
Date: Mon, 05 Oct 2026 23:40:13 +0000 [thread overview]
Message-ID: <179124361377.1939764.6488226653644134516.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260929125143.2890583-1-alexander.sverdlin@siemens.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 29 Sep 2026 14:51:41 +0200 you wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
>
> When bootstrapped with PS_NOWAIT = 0 the internal PHYs stay held in
> reset, so the driver only worked with PS_NOWAIT = 1 where they are
> released automatically.
>
> Add a ->setup() hook, run before the MDIO bus is registered so PHY IDs
> are readable during the bus scan, that programs the RST_REQ PHY reset
> lines: release the PHYs of used ports and hold all other internal PHYs
> in reset. Driving both directions yields the same state regardless of
> the PS_NOWAIT bootstrap and keeps unused PHYs from staying powered.
>
> [...]
Here is the summary with links:
- [net-next,v5] net: dsa: mxl-gsw1xx: force internal PHYs into a known reset state
https://git.kernel.org/netdev/net-next/c/82e2c7db0830
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-05 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 12:51 [PATCH net-next v5] net: dsa: mxl-gsw1xx: force internal PHYs into a known reset state A. Sverdlin
2026-10-05 23:40 ` patchwork-bot+netdevbpf [this message]
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=179124361377.1939764.6488226653644134516.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.sverdlin@siemens.com \
--cc=andrew@lunn.ch \
--cc=daniel@makrotopia.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hauke@hauke-m.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--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 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.