All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Haslam <ahaslam@baylibre.com>
To: broonie@kernel.org, girdwood@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 v3 0/2] regulator: handling of error conditions for usb drivers
Date: Fri,  4 Nov 2016 22:35:34 +0100	[thread overview]
Message-ID: <20161104213536.28496-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 v2 -> v3
* droped merged patch to add new API
* rebased on top of regulator-next

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 (2):
  regulator: fixed: dt: Allow an optional over current pin
  regulator: fixed: Handle optional overcurrent pin

 .../bindings/regulator/fixed-regulator.txt         |  2 +
 drivers/regulator/fixed.c                          | 59 ++++++++++++++++++++++
 2 files changed, 61 insertions(+)

-- 
2.10.1

             reply	other threads:[~2016-11-04 21:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 21:35 Axel Haslam [this message]
     [not found] ` <20161104213536.28496-1-ahaslam-rdvid1DuHRBWk0Htik3J/w@public.gmane.org>
2016-11-04 21:35   ` [PATCH v3 1/2] regulator: fixed: dt: Allow an optional over current pin Axel Haslam
2016-11-04 21:35     ` Axel Haslam
2016-11-14 15:54     ` Rob Herring
2016-11-04 21:35 ` [PATCH v3 2/2] regulator: fixed: Handle optional overcurrent pin Axel Haslam
2016-11-22 16:35 ` [PATCH v3 0/2] regulator: handling of error conditions for usb drivers Axel Haslam
2016-11-22 16:40   ` 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=20161104213536.28496-1-ahaslam@baylibre.com \
    --to=ahaslam@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=david@lechnology.com \
    --cc=girdwood@gmail.com \
    --cc=khilman@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.