From: Florian Fainelli <f.fainelli@gmail.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, s.hauer@pengutronix.de,
b38611@freescale.com, Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH net-next 0/4] net: phy: prevent double suspend
Date: Mon, 26 Jan 2015 16:31:09 -0800 [thread overview]
Message-ID: <1422318673-9418-1-git-send-email-f.fainelli@gmail.com> (raw)
Hi David, Fugang,
This patch series addresses a problem that Fugang and I observed on different
platforms where a given PHY device might end-up being suspended twice.
Once as part of the call from ndo_open() all the way down to phy_detach() and
phy_suspend() and a second time when the generic platform device/driver
suspend/resume callbacks are called in drivers/net/phy/mdio_bus.c.
Fugang, please test this as an alternative to your submission, since it did
break for me on GENET at least. Thanks!
Florian Fainelli (4):
net: phy: utilize phy_suspend and phy_resume
net: phy: document has_fixups field
net: phy: keep track of the PHY suspend state
net: phy: avoid suspending twice a PHY
drivers/net/phy/mdio_bus.c | 14 ++++++++------
drivers/net/phy/phy_device.c | 22 ++++++++++++++++++----
include/linux/phy.h | 3 +++
3 files changed, 29 insertions(+), 10 deletions(-)
--
2.1.0
next reply other threads:[~2015-01-27 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 0:31 Florian Fainelli [this message]
2015-01-27 0:31 ` [PATCH net-next 1/4] net: phy: utilize phy_suspend and phy_resume Florian Fainelli
2015-01-27 2:42 ` fugang.duan
2015-01-27 0:31 ` [PATCH net-next 2/4] net: phy: document has_fixups field Florian Fainelli
2015-01-27 0:31 ` [PATCH net-next 3/4] net: phy: keep track of the PHY suspend state Florian Fainelli
2015-01-27 2:43 ` fugang.duan
2015-01-27 5:55 ` Florian Fainelli
2015-01-27 0:31 ` [PATCH net-next 4/4] net: phy: avoid suspending twice a PHY Florian Fainelli
2015-01-27 2:44 ` 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=1422318673-9418-1-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=b38611@freescale.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).