From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH] devicetree support for ethernet phys
Date: Wed, 21 May 2014 14:18:50 +0200 [thread overview]
Message-ID: <1400674740-6467-1-git-send-email-s.hauer@pengutronix.de> (raw)
This series adds support for specifying ethernet phys in the
devicetree and to connect them with ethernet devices. We already
have beginning support for that used in the orion-gbe driver.
This series has the advantage that the devicetree handling is
completely transparent to the ethernet driver as long as it
fills in the device_nodes of the devices correctly. Also support
for limiting the speed in devicetree is added. This is useful
for boards which have gigabit controllers and gigabit phys but
only 100MBit magnetics.
Sascha
----------------------------------------------------------------
Sascha Hauer (10):
net: phy: factor out phy_device_attach function
net: phy: move setting of phy_map to phy_register_device
net: phy: register phys specified in devicetree
net: phy: Support finding a phy in the devicetree
net: phy: Support limiting phy speed in the devicetree
net: orion-gbe: use transparent-to-driver of mdio functions
net: phy: remove now unused of_phy_device_connect
net: phy: genphy: always write MII_CTRL1000 when available
net: phy: genphy: Make it work with of_set_phy_supported
net: fec_imx: Add devicetree support for mdio bus
drivers/net/fec_imx.c | 5 ++
drivers/net/orion-gbe.c | 62 +++++++++-------
drivers/net/phy/mdio-mvebu.c | 1 +
drivers/net/phy/mdio_bus.c | 107 ++++++++++++++++++++++++++-
drivers/net/phy/phy.c | 169 ++++++++++++++++++++++++-------------------
include/linux/phy.h | 36 ++++-----
6 files changed, 253 insertions(+), 127 deletions(-)
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-05-21 12:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 12:18 Sascha Hauer [this message]
2014-05-21 12:18 ` [PATCH 01/10] net: phy: factor out phy_device_attach function Sascha Hauer
2014-05-21 12:18 ` [PATCH 02/10] net: phy: move setting of phy_map to phy_register_device Sascha Hauer
2014-05-21 12:18 ` [PATCH 03/10] net: phy: register phys specified in devicetree Sascha Hauer
2014-05-21 12:18 ` [PATCH 04/10] net: phy: Support finding a phy in the devicetree Sascha Hauer
2014-05-21 12:18 ` [PATCH 05/10] net: phy: Support limiting phy speed " Sascha Hauer
2014-05-21 12:28 ` Sebastian Hesselbarth
2014-05-21 12:18 ` [PATCH 06/10] net: orion-gbe: use transparent-to-driver of mdio functions Sascha Hauer
2014-05-21 12:29 ` Sebastian Hesselbarth
2014-05-22 20:09 ` Sebastian Hesselbarth
2014-08-02 17:44 ` Ezequiel Garcia
2014-08-04 18:42 ` Sascha Hauer
2014-05-21 12:18 ` [PATCH 07/10] net: phy: remove now unused of_phy_device_connect Sascha Hauer
2014-05-21 12:18 ` [PATCH 08/10] net: phy: genphy: always write MII_CTRL1000 when available Sascha Hauer
2014-05-21 12:18 ` [PATCH 09/10] net: phy: genphy: Make it work with of_set_phy_supported Sascha Hauer
2014-05-21 12:19 ` [PATCH 10/10] net: fec_imx: Add devicetree support for mdio bus 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=1400674740-6467-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