From: patchwork-bot+netdevbpf@kernel.org
To: Dylan Hung <dylan_hung@aspeedtech.com>
Cc: linux-kernel@vger.kernel.org, linux-aspeed@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
andrew@aj.id.au, joel@jms.id.au, kuba@kernel.org,
davem@davemloft.net, linux@armlinux.org.uk, hkallweit1@gmail.com,
andrew@lunn.ch, BMC-SW@aspeedtech.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] mdio: aspeed: Fix "Link is Down" issue
Date: Thu, 25 Nov 2021 16:00:10 +0000 [thread overview]
Message-ID: <163785601008.7926.14064362154729889685.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211125024432.15809-1-dylan_hung@aspeedtech.com>
Hello:
This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 25 Nov 2021 10:44:32 +0800 you wrote:
> The issue happened randomly in runtime. The message "Link is Down" is
> popped but soon it recovered to "Link is Up".
>
> The "Link is Down" results from the incorrect read data for reading the
> PHY register via MDIO bus. The correct sequence for reading the data
> shall be:
> 1. fire the command
> 2. wait for command done (this step was missing)
> 3. wait for data idle
> 4. read data from data register
>
> [...]
Here is the summary with links:
- [v2] mdio: aspeed: Fix "Link is Down" issue
https://git.kernel.org/netdev/net/c/9dbe33cf371b
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-11-25 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 2:44 [PATCH v2] mdio: aspeed: Fix "Link is Down" issue Dylan Hung
2021-11-25 14:47 ` Andrew Lunn
2021-11-25 15:35 ` Russell King (Oracle)
2021-11-25 16:00 ` 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=163785601008.7926.14064362154729889685.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dylan_hung@aspeedtech.com \
--cc=hkallweit1@gmail.com \
--cc=joel@jms.id.au \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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).