From: Axel Haslam <ahaslam@baylibre.com>
To: broonie@kernel.org, lgirdwood@gmail.com, khilman@baylibre.com,
nsekhar@ti.com, david@lechnology.com, robh+dt@kernel.org
Cc: linux-kernel@vger.kernel.org, Axel Haslam <ahaslam@baylibre.com>
Subject: [PATCH/RFC v2 0/3] regulator: handling of error conditions for usb drivers
Date: Thu, 3 Nov 2016 12:11:41 +0100 [thread overview]
Message-ID: <20161103111144.511-1-ahaslam@baylibre.com> (raw)
Some usb drivers rely on external power switches/regulators
to for the port vbus. Some of these drivers are using
a plain gpio for the enable pin and also the over current
indicator pin.
To make these drivers more generic, we can use a regulator
to handle vbus, and send and over current event, but we are
missing a way to transmit the over current pin status, which
the usb layer may poll at any time.
We would like to move these drivers to use a regulator, this
would make the usb driver generic allowing to use any type
of regulator. Also, it would help removing code, making DT
migration simpler and avoiding new DT bindings for each driver.
These patches do 2 things:
* Add a new API, that consumers can use to poll the regulator
error status.
* Extends the fixed regulator driver to handle an optional
over current gpio pin.
Changes v1->v2
* add new API to get error status instead of extending events (Mark)
* use gpiod for fixed regulator: This spears us extra platform
data and bindings
Axel Haslam (3):
regulator: core: Add new API to poll for error conditions
regulator: fixed: dt: Allow an optional over current pin
regulator: fixed: Handle optional overcurrent pin
.../bindings/regulator/fixed-regulator.txt | 2 +
drivers/regulator/core.c | 33 ++++++++++++
drivers/regulator/fixed.c | 60 ++++++++++++++++++++++
include/linux/regulator/consumer.h | 26 ++++++++++
include/linux/regulator/driver.h | 4 ++
5 files changed, 125 insertions(+)
--
2.10.1
next reply other threads:[~2016-11-03 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 11:11 Axel Haslam [this message]
2016-11-03 11:11 ` [PATCH/RFC v2 1/3] regulator: core: Add new API to poll for error conditions Axel Haslam
2016-11-04 18:16 ` Applied "regulator: core: Add new API to poll for error conditions" to the regulator tree Mark Brown
2016-11-03 11:11 ` [PATCH/RFC v2 2/3] regulator: fixed: dt: Allow an optional over current pin Axel Haslam
2016-11-03 11:11 ` [PATCH/RFC v2 3/3] regulator: fixed: Handle optional overcurrent pin Axel Haslam
2016-11-04 18:20 ` Mark Brown
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=20161103111144.511-1-ahaslam@baylibre.com \
--to=ahaslam@baylibre.com \
--cc=broonie@kernel.org \
--cc=david@lechnology.com \
--cc=khilman@baylibre.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=robh+dt@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
Powered by JetHome