From: Florian Fainelli <f.fainelli@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>,
Jisheng Zhang <Jisheng.Zhang@synaptics.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] net: phy: add shutdown hook to struct phy_driver
Date: Wed, 30 Sep 2020 13:07:19 -0700 [thread overview]
Message-ID: <bab6c68f-8ed7-26b7-65ed-a65c7210e691@gmail.com> (raw)
In-Reply-To: <20200930190911.GU3996795@lunn.ch>
On 9/30/2020 12:09 PM, Andrew Lunn wrote:
> On Wed, Sep 30, 2020 at 05:47:43PM +0800, Jisheng Zhang wrote:
>> Hi,
>>
>> A GE phy supports pad isolation which can save power in WOL mode. But once the
>> isolation is enabled, the MAC can't send/receive pkts to/from the phy because
>> the phy is "isolated". To make the PHY work normally, I need to move the
>> enabling isolation to suspend hook, so far so good. But the isolation isn't
>> enabled in system shutdown case, to support this, I want to add shutdown hook
>> to net phy_driver, then also enable the isolation in the shutdown hook. Is
>> there any elegant solution?
>
>> Or we can break the assumption: ethernet can still send/receive pkts after
>> enabling WoL, no?
>
> That is not an easy assumption to break. The MAC might be doing WOL,
> so it needs to be able to receive packets.
>
> What you might be able to assume is, if this PHY device has had WOL
> enabled, it can assume the MAC does not need to send/receive after
> suspend. The problem is, phy_suspend() will not call into the driver
> is WOL is enabled, so you have no idea when you can isolate the MAC
> from the PHY.
>
> So adding a shutdown in mdio_driver_register() seems reasonable. But
> you need to watch out for ordering. Is the MDIO bus driver still
> running?
If your Ethernet MAC controller implements a shutdown callback and that
callback takes care of unregistering the network device which should
also ensure that phy_disconnect() gets called, then your PHY's suspend
function will be called.
--
Florian
next prev parent reply other threads:[~2020-09-30 20:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 9:47 [RFC] net: phy: add shutdown hook to struct phy_driver Jisheng Zhang
2020-09-30 19:09 ` Andrew Lunn
2020-09-30 20:07 ` Florian Fainelli [this message]
2020-09-30 20:11 ` Andrew Lunn
2020-09-30 20:23 ` Florian Fainelli
2020-10-05 8:53 ` Jisheng Zhang
2020-10-05 15:41 ` Florian Fainelli
2020-10-05 15:54 ` Heiner Kallweit
2020-10-05 16:00 ` Florian Fainelli
2020-10-06 5:45 ` Heiner Kallweit
2020-10-06 7:17 ` Jisheng Zhang
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=bab6c68f-8ed7-26b7-65ed-a65c7210e691@gmail.com \
--to=f.fainelli@gmail.com \
--cc=Jisheng.Zhang@synaptics.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.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).