netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Florian Fainelli" <f.fainelli@gmail.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, afleming@freescale.com, jogo@openwrt.org,
	"Florian Fainelli" <f.fainelli@gmail.com>
Subject: [PATCH 0/2 net-next] phy: allow flagging a device as internal
Date: Tue, 21 May 2013 11:37:04 +0100	[thread overview]
Message-ID: <1369132626-13776-1-git-send-email-f.fainelli@gmail.com> (raw)

David, Andy,

This small patch set updates libphy to allow PHY drivers to flag a
specific PHY device as internal, which is then used to accurately
report the transceiver type (internal vs external) in ethtool.

As far as I can tell we only have one in-tree driver for the moment
which is known to be for internal PHYs.

Florian Fainelli (2):
  phy: allow drivers to flag a PHY device as internal
  phy: bcm63xx: report Broadcom BCM63xx PHYs as internal

 drivers/net/phy/bcm63xx.c    | 4 ++--
 drivers/net/phy/phy.c        | 2 +-
 drivers/net/phy/phy_device.c | 3 +++
 include/linux/phy.h          | 3 +++
 4 files changed, 9 insertions(+), 3 deletions(-)

-- 
1.8.1.2

             reply	other threads:[~2013-05-21 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21 10:37 Florian Fainelli [this message]
2013-05-21 10:37 ` [PATCH 1/2 net-next] phy: allow drivers to flag a PHY device as internal Florian Fainelli
2013-05-21 10:37 ` [PATCH 2/2 net-next] phy: bcm63xx: report Broadcom BCM63xx PHYs " Florian Fainelli
2013-05-21 16:44 ` [PATCH 0/2 net-next] phy: allow flagging a device " Ben Hutchings
2013-05-21 17:35   ` Fleming Andy-AFLEMING
     [not found]   ` <CAGVrzcbN1LLdC6ASLhk4e+33pr4aP3xBeycQ_kiL09VxVTmitg@mail.gmail.com>
2013-05-21 17:48     ` Ben Hutchings

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=1369132626-13776-1-git-send-email-f.fainelli@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=afleming@freescale.com \
    --cc=davem@davemloft.net \
    --cc=jogo@openwrt.org \
    --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).