From: patchwork-bot+netdevbpf@kernel.org
To: Francesco Dolcini <francesco.dolcini@toradex.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, kuba@kernel.org,
nicolas.ferre@microchip.com, bbrezillon@kernel.org,
patrice.vilchez@atmel.com, stefan@agner.ch, f.fainelli@gmail.com,
christophe.leroy@csgroup.eu, sergei.shtylyov@gmail.com,
marcel.ziswiler@toradex.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] phy: micrel: ksz8041nl: do not use power down mode
Date: Wed, 20 Oct 2021 13:40:07 +0000 [thread overview]
Message-ID: <163473720705.8032.5657511877917396635.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211019191647.346361-1-francesco.dolcini@toradex.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 19 Oct 2021 21:16:47 +0200 you wrote:
> From: Stefan Agner <stefan@agner.ch>
>
> Some Micrel KSZ8041NL PHY chips exhibit continuous RX errors after using
> the power down mode bit (0.11). If the PHY is taken out of power down
> mode in a certain temperature range, the PHY enters a weird state which
> leads to continuously reporting RX errors. In that state, the MAC is not
> able to receive or send any Ethernet frames and the activity LED is
> constantly blinking. Since Linux is using the suspend callback when the
> interface is taken down, ending up in that state can easily happen
> during a normal startup.
>
> [...]
Here is the summary with links:
- [net-next,v2] phy: micrel: ksz8041nl: do not use power down mode
https://git.kernel.org/netdev/net-next/c/2641b62d2fab
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-10-20 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 19:16 [PATCH net-next v2] phy: micrel: ksz8041nl: do not use power down mode Francesco Dolcini
2021-10-20 13:40 ` 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=163473720705.8032.5657511877917396635.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=bbrezillon@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marcel.ziswiler@toradex.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=patrice.vilchez@atmel.com \
--cc=sergei.shtylyov@gmail.com \
--cc=stefan@agner.ch \
/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.