From: Florian Fainelli <f.fainelli@gmail.com>
To: <netdev@vger.kernel.org>
Cc: <davem@davemloft.net>, <sebastian.hesselbarth@gmail.com>,
<sergei.shtylyov@cogentembedded.com>, <afleming@gmail.com>,
<kyle@moffetthome.net>, Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH 0/9] net: phy: PHY reset consolidation
Date: Thu, 5 Dec 2013 16:55:08 -0800 [thread overview]
Message-ID: <1386291317-1202-1-git-send-email-f.fainelli@gmail.com> (raw)
Hi all,
Over the past few months there have been various attempts at doing
"wild" PHY resets eventually bypassing the PHY state machine and causing
various sort of issues whenever auto-negotiation as not enabled.
This patchset resumes the work Kyle Moffett started here:
https://lkml.org/lkml/2011/10/20/301
Once Sebastian's phy_resume/suspend patchet is in, we can also make sure
we consolidate PHY resets after resuming from S2/S3 suspend modes.
Florian Fainelli (9):
net: phy: report link partner features through ethtool
net: phy: use phy_init_hw instead of open-coding it
net: greth: use phy_read_status()
net: bfin_mac: do not reset PHY after phy_start()
net: phy: consolidate PHY reset in phy_init_hw()
net: mv643xx_eth: use phy_init_hw to reset PHY
net: pxa168_eth: use phy_init_hw for PHY reset
net: tc35815: use phy_init_hw for PHY reset
net: sh_eth: do not issue a wild PHY reset through BMCR
Documentation/networking/phy.txt | 3 +-
drivers/net/ethernet/adi/bfin_mac.c | 1 -
drivers/net/ethernet/aeroflex/greth.c | 2 +-
drivers/net/ethernet/marvell/mv643xx_eth.c | 21 +---------
drivers/net/ethernet/marvell/pxa168_eth.c | 19 +--------
drivers/net/ethernet/renesas/sh_eth.c | 5 ++-
drivers/net/ethernet/toshiba/tc35815.c | 15 ++------
drivers/net/phy/phy.c | 11 +++---
drivers/net/phy/phy_device.c | 62 +++++++++++++++++++++++++++++-
include/linux/phy.h | 5 ++-
10 files changed, 82 insertions(+), 62 deletions(-)
--
1.8.3.2
next reply other threads:[~2013-12-06 1:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 0:55 Florian Fainelli [this message]
2013-12-06 0:55 ` [PATCH 1/9] net: phy: report link partner features through ethtool Florian Fainelli
2013-12-06 0:55 ` [PATCH 2/9] net: phy: use phy_init_hw instead of open-coding it Florian Fainelli
2013-12-06 0:55 ` [PATCH 3/9] net: greth: use phy_read_status() Florian Fainelli
2013-12-06 0:55 ` [PATCH 4/9] net: bfin_mac: do not reset PHY after phy_start() Florian Fainelli
2013-12-06 0:55 ` [PATCH 5/9] net: phy: consolidate PHY reset in phy_init_hw() Florian Fainelli
2013-12-06 0:55 ` [PATCH 6/9] net: mv643xx_eth: use phy_init_hw to reset PHY Florian Fainelli
2013-12-06 2:16 ` Sergei Shtylyov
2013-12-06 0:55 ` [PATCH 7/9] net: pxa168_eth: use phy_init_hw for PHY reset Florian Fainelli
2013-12-06 1:06 ` Florian Fainelli
2013-12-06 0:55 ` [PATCH 8/9] net: tc35815: " Florian Fainelli
2013-12-06 0:55 ` [PATCH 9/9] net: sh_eth: do not issue a wild PHY reset through BMCR Florian Fainelli
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=1386291317-1202-1-git-send-email-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=afleming@gmail.com \
--cc=davem@davemloft.net \
--cc=kyle@moffetthome.net \
--cc=netdev@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
/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).