From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: mii patches
Date: Wed, 11 Dec 2013 12:41:08 +0100 [thread overview]
Message-ID: <1386762077-23205-1-git-send-email-s.hauer@pengutronix.de> (raw)
This makes mii phys found on mii buses available independently of
networks devices. Also it makes all phy devices visible to the
user, not only the one attached to an ethernet device. This makes
the miitool command (or simpler: md -w -s /dev/phyx) more useful
The current mii code allows to only register a phy device when
there's an ethernet device around. This dependency is removed so
that it's possible to register phys without ethernet devices.
With this series the miitool gets a -s option to scan all registered
mii buses for devices which can be examined afterwards. This is
implemented with the device 'detect' mechanism, so a 'detect -a'
or 'detect miibus0' is also possible to detect phys.
Sascha
----------------------------------------------------------------
Sascha Hauer (9):
net: phy: cleanup attached device handling
net: phy: bail out early in phy_device_connect
net: phy: move duplicated code out of if/else
net: phy: check if a phy already has an ethernet device
net: phy: track registered state of a phy device
net: phy: move phy_init_hw to phy_device_connect
net: phy: Track mii buses on a list
net: phy: implement detect callback for miibus devices
miitool: Add option to scan mii buses
commands/miitool.c | 12 ++++-
drivers/net/phy/mdio_bus.c | 49 ++++++++++++++++-----
drivers/net/phy/phy.c | 106 ++++++++++++++++++++++++++-------------------
include/linux/phy.h | 12 +++++
4 files changed, 120 insertions(+), 59 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2013-12-11 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 11:41 Sascha Hauer [this message]
2013-12-11 11:41 ` [PATCH 1/9] net: phy: cleanup attached device handling Sascha Hauer
2013-12-11 11:41 ` [PATCH 2/9] net: phy: bail out early in phy_device_connect Sascha Hauer
2013-12-11 11:41 ` [PATCH 3/9] net: phy: move duplicated code out of if/else Sascha Hauer
2013-12-11 11:41 ` [PATCH 4/9] net: phy: check if a phy already has an ethernet device Sascha Hauer
2013-12-11 11:41 ` [PATCH 5/9] net: phy: track registered state of a phy device Sascha Hauer
2013-12-11 11:41 ` [PATCH 6/9] net: phy: move phy_init_hw to phy_device_connect Sascha Hauer
2013-12-11 11:41 ` [PATCH 7/9] net: phy: Track mii buses on a list Sascha Hauer
2013-12-11 11:41 ` [PATCH 8/9] net: phy: implement detect callback for miibus devices Sascha Hauer
2013-12-11 11:41 ` [PATCH 9/9] miitool: Add option to scan mii buses Sascha Hauer
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=1386762077-23205-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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