From: <Claudiu.Beznea@microchip.com>
To: <linux@armlinux.org.uk>
Cc: <hkallweit1@gmail.com>, <andrew@lunn.ch>, <davem@davemloft.net>,
<kuba@kernel.org>, <rjw@rjwysocki.net>, <pavel@ucw.cz>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-pm@vger.kernel.org>
Subject: Re: [PATCH] net: phy: micrel: reconfigure the phy on resume
Date: Thu, 14 Jan 2021 10:41:46 +0000 [thread overview]
Message-ID: <fe4c31a0-b807-0eb2-1223-c07d7580e1fc@microchip.com> (raw)
In-Reply-To: <20210114102508.GO1551@shell.armlinux.org.uk>
On 14.01.2021 12:25, Russell King - ARM Linux admin wrote:
>
> As I've said, if phylib/PHY driver is not restoring the state of the
> PHY on resume from suspend-to-ram, then that's an issue with phylib
> and/or the phy driver.
In the patch I proposed in this thread the restoring is done in PHY driver.
Do you think I should continue the investigation and check if something
should be done from the phylib itself?
Thank you,
Claudiu Beznea
>
> --
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
>
next prev parent reply other threads:[~2021-01-14 10:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 15:45 [PATCH] net: phy: micrel: reconfigure the phy on resume Claudiu Beznea
2021-01-08 16:10 ` Andrew Lunn
2021-01-08 16:31 ` Heiner Kallweit
2021-01-13 9:29 ` Claudiu.Beznea
2021-01-13 11:09 ` Heiner Kallweit
2021-01-13 12:36 ` Claudiu.Beznea
2021-01-13 21:34 ` Heiner Kallweit
2021-01-13 22:01 ` Russell King - ARM Linux admin
2021-01-14 7:30 ` Heiner Kallweit
2021-01-14 10:12 ` Claudiu.Beznea
2021-01-14 10:25 ` Russell King - ARM Linux admin
2021-01-14 10:41 ` Claudiu.Beznea [this message]
2021-01-14 11:05 ` Heiner Kallweit
2021-02-11 11:18 ` Claudiu.Beznea
2021-02-11 12:17 ` Pavel Machek
2021-02-11 12:36 ` Heiner Kallweit
2021-02-11 20:34 ` Pavel Machek
2021-01-13 23:28 ` Jakub Kicinski
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=fe4c31a0-b807-0eb2-1223-c07d7580e1fc@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
/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).