From: patchwork-bot+netdevbpf@kernel.org
To: Hongmei Xu <hongmei.xu@oss.qualcomm.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
sagar.cheluvegowda@oss.qualcomm.com
Subject: Re: [PATCH net-next v4] net: phy: aquantia: Poll global status register for provision ID
Date: Fri, 20 Nov 2026 02:10:11 +0000 [thread overview]
Message-ID: <179514061177.3979015.6848094959866976600.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261116-aquantia-poll-global-status-register-v4-1-1b44fe85db5a@oss.qualcomm.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 16 Nov 2026 19:14:50 +0800 you wrote:
> According to the AQR113 PHY databook, after firmware reset, a 20ms
> timer needs to be engaged to allow the supplies to settle prior to
> allowing the PHY to boot. The working flow is:
> -After the 20 ms timer has completed, hardware state machines
> designed to guarantee PLL and band-gap stability engage.
> -After the PLLs and band-gap are locked and functioning properly,
> the processor and digital circuitry are released from reset.
> -The PHY image is then loaded through MDIO boot-load and the
> processor boots.
> -After the processor boots, any provisioned register values are
> set, and the PHY enters the provisioned operating state.
>
> [...]
Here is the summary with links:
- [net-next,v4] net: phy: aquantia: Poll global status register for provision ID
https://git.kernel.org/netdev/net-next/c/d3f362a76211
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-11-20 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 11:14 [PATCH net-next v4] net: phy: aquantia: Poll global status register for provision ID Hongmei Xu
2026-11-16 13:33 ` Andrew Lunn
2026-11-18 17:17 ` netdev-bot+sashiko
2026-11-19 3:28 ` Hongmei Xu
2026-11-20 2:10 ` 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=179514061177.3979015.6848094959866976600.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=hongmei.xu@oss.qualcomm.com \
--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=sagar.cheluvegowda@oss.qualcomm.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.