From: patchwork-bot+netdevbpf@kernel.org
To: Yongzhao Chen <yongzhao.derek@gmail.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, george.moussalem@outlook.com,
hzyitc@outlook.com, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] net: phy: qcom: at803x: Apply IPQ5018 analog settings at probe
Date: Fri, 16 Oct 2026 15:30:05 +0000 [thread overview]
Message-ID: <179216460528.820266.15057930452700501966.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261002210408.730-1-yongzhao.derek@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 2 Oct 2026 23:04:08 +0200 you wrote:
> ipq5018_probe() pulses the PHY reset, after which the IPQ5018 internal
> GE PHY starts autonegotiating with its reset-default analog settings.
> ipq5018_config_init() writes the analog settings only when the MAC
> attaches the PHY, usually when the interface is opened. On a board
> where the PHY connects to a QCA8337 PHY without a cable, 1000BASE-T
> does not come up in the meantime, SmartSpeed downshifts both PHYs, and
> only the IPQ5018 side restores its 1000BASE-T advertisement at attach,
> so the link stays down.
>
> [...]
Here is the summary with links:
- [net,v3] net: phy: qcom: at803x: Apply IPQ5018 analog settings at probe
https://git.kernel.org/netdev/net-next/c/17baf30a0e64
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-16 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 21:04 [PATCH net v3] net: phy: qcom: at803x: Apply IPQ5018 analog settings at probe Yongzhao Chen
2026-10-03 21:21 ` netdev-bot+sashiko
2026-10-08 16:55 ` Jakub Kicinski
2026-10-08 19:35 ` Yongzhao Chen
2026-10-16 15:30 ` 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=179216460528.820266.15057930452700501966.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=george.moussalem@outlook.com \
--cc=hkallweit1@gmail.com \
--cc=hzyitc@outlook.com \
--cc=kuba@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yongzhao.derek@gmail.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