From: David Bauer <mail@david-bauer.net>
To: devicetree@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH v3 0/3] net: add reset-controller driven PHY reset
Date: Wed, 17 Apr 2019 23:59:19 +0200 [thread overview]
Message-ID: <20190417215922.30472-1-mail@david-bauer.net> (raw)
This patchset adds support for a PHY reset driven by a reset-controller.
Currently, only GPIO driven resets are supported by the PHY subsystem.
It also renames the reset-gpio from 'reset' to 'reset_gpio' to
better differentiate between resets wired to a GPIO and resets wired to
a reset-controller driven pin.
Some systems have the PHY reset-line wired to a pin controlled by a
reset-controller (eg. some Atheros AR9132 based boards). In case the
bootloader asserts reset before loading the kernel, we currently do not
have a clean way of deasserting reset to probe the PHY.
v3:
- add missing newline in mdio_bus.c
v2:
- fixed missed rename of "reset" in at803x.c
- move initial reset to mdio_device_reset
David Bauer (3):
dt-bindings: net: add PHY reset controller binding
net: phy: add support for reset-controller
net: mdio: rename mdio_device reset to reset_gpio
Documentation/devicetree/bindings/net/phy.txt | 6 ++++
drivers/net/phy/at803x.c | 2 +-
drivers/net/phy/mdio_bus.c | 33 ++++++++++++++++---
drivers/net/phy/mdio_device.c | 13 ++++++--
include/linux/mdio.h | 3 +-
5 files changed, 48 insertions(+), 9 deletions(-)
--
2.21.0
next reply other threads:[~2019-04-17 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 21:59 David Bauer [this message]
2019-04-17 21:59 ` [PATCH v3 1/3] dt-bindings: net: add PHY reset controller binding David Bauer
2019-04-17 22:15 ` Andrew Lunn
2019-04-17 21:59 ` [PATCH v3 2/3] net: phy: add support for reset-controller David Bauer
2019-04-17 22:16 ` Andrew Lunn
2019-04-17 21:59 ` [PATCH v3 3/3] net: mdio: rename mdio_device reset to reset_gpio David Bauer
2019-04-17 22:17 ` Andrew Lunn
2019-04-19 0:43 ` [PATCH v3 0/3] net: add reset-controller driven PHY reset 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=20190417215922.30472-1-mail@david-bauer.net \
--to=mail@david-bauer.net \
--cc=devicetree@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).