From: patchwork-bot+netdevbpf@kernel.org
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: hauke@hauke-m.de, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, andrew@lunn.ch,
vivien.didelot@gmail.com, f.fainelli@gmail.com,
olteanv@gmail.com, davem@davemloft.net, kuba@kernel.org
Subject: Re: [PATCH net] net: dsa: lantiq_gswip: Let GSWIP automatically set the xMII clock
Date: Fri, 26 Mar 2021 00:30:10 +0000 [thread overview]
Message-ID: <161671861063.2256.3129644710566054150.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210324193604.1433230-1-martin.blumenstingl@googlemail.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Wed, 24 Mar 2021 20:36:04 +0100 you wrote:
> The xMII interface clock depends on the PHY interface (MII, RMII, RGMII)
> as well as the current link speed. Explicitly configure the GSWIP to
> automatically select the appropriate xMII interface clock.
>
> This fixes an issue seen by some users where ports using an external
> RMII or RGMII PHY were deaf (no RX or TX traffic could be seen). Most
> likely this is due to an "invalid" xMII clock being selected either by
> the bootloader or hardware-defaults.
>
> [...]
Here is the summary with links:
- [net] net: dsa: lantiq_gswip: Let GSWIP automatically set the xMII clock
https://git.kernel.org/netdev/net/c/3e6fdeb28f4c
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:[~2021-03-26 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 19:36 [PATCH net] net: dsa: lantiq_gswip: Let GSWIP automatically set the xMII clock Martin Blumenstingl
2021-03-25 18:09 ` Florian Fainelli
2021-03-25 18:31 ` Martin Blumenstingl
2021-03-26 0: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=161671861063.2256.3129644710566054150.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@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;
as well as URLs for NNTP newsgroup(s).