From: Florian Fainelli <f.fainelli@gmail.com>
To: Fugang Duan <b38611@freescale.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, s.hauer@pengutronix.de,
bhutchings@solarflare.com, stephen@networkplumber.org
Subject: Re: [PATCH net-next 1/1] net: phy: unbind phy device from generic and specifical driver
Date: Mon, 26 Jan 2015 09:47:03 -0800 [thread overview]
Message-ID: <54C67D97.7080203@gmail.com> (raw)
In-Reply-To: <54C675F1.9080803@gmail.com>
On 26/01/15 09:14, Florian Fainelli wrote:
> On 26/01/15 00:14, Fugang Duan wrote:
>> The current .phy_detach() function only unbind generic phy driver, which causes
>> specifical driver suspend/resume function still work like Atheros AT803X PHYs.
>>
>> For example:
>> ifconfig eth0 down
>> echo mem > /sys/power/status
>>
>> After eth0 interface down, driver call phy_detach to unbind phy driver, and then
>> do suspend/resume operation, at803x_suspend()/at803x_resume() functions still get
>> called that call mdio bus read/write function. When eth0 interface down, MAC driver
>> may close all clocks and mdio bus cannot work. So the issue happens.
>
> I was just hitting this problem on Friday evening and was about to
> submit a similar change. Thanks!
>
>>
>> The patch can unbind generic and specifical driver.
>>
>> Signed-off-by: Fugang Duan <B38611@freescale.com>
>
> Acked-by: Florian Fainelli <f.fainelli@gmail.com>
> Tested-by: Florian Fainelli <f.fainelli@gmail.com>
Humm, this breaks a sequence of ifconfig down then up, the driver is
removed, and we never get to probe it again, does this work for you
using the FEC driver?
Another way to solve this double suspend problem is to make sure that we
track whether the PHY has already been suspended.
--
Florian
next prev parent reply other threads:[~2015-01-26 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 8:14 [PATCH net-next 1/1] net: phy: unbind phy device from generic and specifical driver Fugang Duan
2015-01-26 17:14 ` Florian Fainelli
2015-01-26 17:47 ` Florian Fainelli [this message]
2015-01-27 2:27 ` fugang.duan
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=54C67D97.7080203@gmail.com \
--to=f.fainelli@gmail.com \
--cc=b38611@freescale.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=stephen@networkplumber.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).