From: patchwork-bot+netdevbpf@kernel.org
To: Dylan Hung <dylan_hung@aspeedtech.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
guoheyi@linux.alibaba.com, huangguangbin2@huawei.com,
chenhao288@hisilicon.com, yangyingliang@huawei.com,
joel@jms.id.au, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, BMC-SW@aspeedtech.com
Subject: Re: [PATCH] net: ftgmac100: access hardware register after clock ready
Date: Wed, 13 Apr 2022 11:50:11 +0000 [thread overview]
Message-ID: <164985061139.24768.4926200477271415631.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220412114859.18665-1-dylan_hung@aspeedtech.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 12 Apr 2022 19:48:59 +0800 you wrote:
> AST2600 MAC register 0x58 is writable only when the MAC clock is
> enabled. Usually, the MAC clock is enabled by the bootloader so
> register 0x58 is set normally when the bootloader is involved. To make
> ast2600 ftgmac100 work without the bootloader, postpone the register
> write until the clock is ready.
>
> Fixes: 137d23cea1c0 ("net: ftgmac100: Fix Aspeed ast2600 TX hang issue")
> Signed-off-by: Dylan Hung <dylan_hung@aspeedtech.com>
>
> [...]
Here is the summary with links:
- net: ftgmac100: access hardware register after clock ready
https://git.kernel.org/netdev/net/c/3d2504524531
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:[~2022-04-13 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 11:48 [PATCH] net: ftgmac100: access hardware register after clock ready Dylan Hung
2022-04-13 11:50 ` 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=164985061139.24768.4926200477271415631.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=BMC-SW@aspeedtech.com \
--cc=chenhao288@hisilicon.com \
--cc=davem@davemloft.net \
--cc=dylan_hung@aspeedtech.com \
--cc=guoheyi@linux.alibaba.com \
--cc=huangguangbin2@huawei.com \
--cc=joel@jms.id.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yangyingliang@huawei.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