mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: 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 21:09:11 +0200	[thread overview]
Message-ID: <20200930190911.GU3996795@lunn.ch> (raw)
In-Reply-To: <20200930174419.345cc9b4@xhacker.debian>

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?

   Andrew

  reply	other threads:[~2020-09-30 19:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30  9:47 Jisheng Zhang
2020-09-30 19:09 ` Andrew Lunn [this message]
2020-09-30 20:07   ` Florian Fainelli
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=20200930190911.GU3996795@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Jisheng.Zhang@synaptics.com \
    --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

all inboxes | Powered by JetHome®