From: Guenter Roeck <linux@roeck-us.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Chris Healy <chealy@imsco-us.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Guenter Roeck <linux@roeck-us.net>
Subject: [PATCH 0/3] net: mdio-gpio enhancements
Date: Tue, 15 Apr 2014 19:16:39 -0700 [thread overview]
Message-ID: <1397614602-29694-1-git-send-email-linux@roeck-us.net> (raw)
The following series of patches adds support for active-low gpio pins
as well as for systems with separate MDI and MDO pins to the mdio-gpio
driver.
A board using those features is based on a COM Express CPU board.
The COM Express standard supports GPIO pins on its connector,
with one caveat: The pins on the connector have fixed direction
and are hard configured either as input or output pins.
The COM Express Design Guide [1] provides additional details.
The hardware uses three of the GPO/GPI pins from the COM Express board
to drive an MDIO bus. Connectivity between GPI/GPO pins and the MDIO bus
is as follows.
GPI2 --------------------+------------ MDIO
|
+--------+ |
GPO2 ---+---G | |
| | | |
4.7k | 2N7002 D---+
| | |
+---S |
| +--------+
GND
GPO1 --------------------------------- MDC
To support this hardware, two extensions to the driver were necessary.
- Due to the FET in the MDO path (GPO2), the MDO signal is inverted.
The driver therefore has to support active-low GPIO pins.
- The MDIO signal must be separated into MDI and MDO.
Those changes are implemented in patch 2/3 and 3/3.
Patch 1/3 simplifies the error path and thus the subsequent
patches.
[1] http://www.picmg.org/pdf/picmg_comdg_100.pdf
----------------------------------------------------------------
Guenter Roeck (3):
net: mdio-gpio: Use devm_ functions where possible
net: mdio-gpio: Add support for active low gpio pins
net: mdio-gpio: Add support for separate MDI and MDO gpio pins
drivers/net/phy/mdio-gpio.c | 68 ++++++++++++++++++++++++++++++-------------
include/linux/mdio-gpio.h | 5 ++++
2 files changed, 52 insertions(+), 21 deletions(-)
next reply other threads:[~2014-04-16 2:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 2:16 Guenter Roeck [this message]
2014-04-16 2:16 ` [PATCH 1/3] net: mdio-gpio: Use devm_ functions where possible Guenter Roeck
2014-04-16 2:50 ` Chris Healy
2014-04-16 3:17 ` David Miller
2014-04-16 18:48 ` Chris Healy
2014-04-16 18:50 ` Chris Healy
2014-04-16 20:22 ` Guenter Roeck
2014-04-18 19:19 ` Sergei Shtylyov
2014-04-16 2:16 ` [PATCH 2/3] net: mdio-gpio: Add support for active low gpio pins Guenter Roeck
2014-04-16 2:44 ` Chris Healy
2014-04-16 2:16 ` [PATCH 3/3] net: mdio-gpio: Add support for separate MDI and MDO " Guenter Roeck
2014-04-16 2:45 ` Chris Healy
2014-04-16 19:10 ` [PATCH 0/3] net: mdio-gpio enhancements David Miller
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=1397614602-29694-1-git-send-email-linux@roeck-us.net \
--to=linux@roeck-us.net \
--cc=chealy@imsco-us.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.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).