From: patchwork-bot+netdevbpf@kernel.org
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: andrew@lunn.ch, linux@armlinux.org.uk, kuba@kernel.org,
davem@davemloft.net, Claudiu.Beznea@microchip.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net] net: phy: consider that suspend2ram may cut off PHY power
Date: Fri, 12 Feb 2021 02:30:07 +0000 [thread overview]
Message-ID: <161309700700.16682.9228652055785839659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <fcd4c005-22b0-809b-4474-0435313a5a47@gmail.com>
Hello:
This patch was applied to netdev/net.git (refs/heads/master):
On Thu, 11 Feb 2021 22:32:52 +0100 you wrote:
> Claudiu reported that on his system S2R cuts off power to the PHY and
> after resuming certain PHY settings are lost. The PM folks confirmed
> that cutting off power to selected components in S2R is a valid case.
> Therefore resuming from S2R, same as from hibernation, has to assume
> that the PHY has power-on defaults. As a consequence use the restore
> callback also as resume callback.
> In addition make sure that the interrupt configuration is restored.
> Let's do this in phy_init_hw() and ensure that after this call
> actual interrupt configuration is in sync with phydev->interrupts.
> Currently, if interrupt was enabled before hibernation, we would
> resume with interrupt disabled because that's the power-on default.
>
> [...]
Here is the summary with links:
- [net] net: phy: consider that suspend2ram may cut off PHY power
https://git.kernel.org/netdev/net/c/4c0d2e96ba05
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-02-12 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 21:32 [PATCH net] net: phy: consider that suspend2ram may cut off PHY power Heiner Kallweit
2021-02-12 2:30 ` patchwork-bot+netdevbpf [this message]
2021-02-12 11:43 ` Claudiu.Beznea
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=161309700700.16682.9228652055785839659.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Claudiu.Beznea@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@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).