From: Vince Bridgers <vbridgers2013@gmail.com>
To: f.fainelli@gmail.com, netdev@vger.kernel.org
Cc: vbridgers2013@gmail.com
Subject: [PATCH net V2 0/2] libphy: Add phy specific function to access mmd
Date: Thu, 29 May 2014 11:28:31 -0500 [thread overview]
Message-ID: <1401380913-4207-1-git-send-email-vbridgers2013@gmail.com> (raw)
This set of patches addresses a problem found with the Micrel ksz9021 phy and
libphy, where the ksz9021 phy does not support mmd extended register access
per the IEEE specification as assumed by libphy. The first patch adds a
framework for phy specific support to specify their own function to access
extended phy registers, return a failure code if not supported, or to default
to libphy's IEEE defined method for accessing the mmd extended phy registers.
This issue was found by using the Synopsys EMAC and a Micrel ksz9021 phy on the
Altera Cyclone 5 SOC development kit. This patch was tested on the same system
in both positive and negative test cases.
Please consider including this patch if you find these modifications
acceptable.
---
V2: Split the original patch submission into seperate patches for the libphy
framework required for the modification and for the Micrel Phy.
Vince Bridgers (2):
libphy: Add phy specific function to access mmd phy registers
libphy: Add stubs to hook IEEE MMD Register reads and writes
drivers/net/phy/micrel.c | 23 ++++++++++++++++++++
drivers/net/phy/phy.c | 49 ++++++++++++++++++++++--------------------
drivers/net/phy/phy_device.c | 6 ++++++
include/linux/phy.h | 10 +++++++++
4 files changed, 65 insertions(+), 23 deletions(-)
--
1.7.9.5
next reply other threads:[~2014-05-29 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 16:28 Vince Bridgers [this message]
2014-05-29 16:28 ` [PATCH net V2 1/2] libphy: Add phy specific function to access mmd phy registers Vince Bridgers
2014-06-02 21:12 ` David Miller
2014-05-29 16:28 ` [PATCH net V2 2/2] libphy: Add stubs to hook IEEE MMD Register reads and writes Vince Bridgers
2014-05-29 20:17 ` Sergei Shtylyov
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=1401380913-4207-1-git-send-email-vbridgers2013@gmail.com \
--to=vbridgers2013@gmail.com \
--cc=f.fainelli@gmail.com \
--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).