mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ahaslam@baylibre.com
To: broonie@kernel.org, lgirdwood@gmail.com, khilman@baylibre.com,
	nsekhar@ti.com, david@lechnology.com
Cc: linux-kernel@vger.kernel.org, Axel Haslam <ahaslam@baylibre.com>
Subject: [PATCH 0/3] regulator: Send events on over current condition
Date: Wed, 26 Oct 2016 21:00:51 +0200	[thread overview]
Message-ID: <20161026190054.11968-1-ahaslam@baylibre.com> (raw)

From: Axel Haslam <ahaslam@baylibre.com>

Some usb drivers rely on external power switches/regulators to handle
the port vbus. Some of these drivers currently are still using gpios for
the enable pin and also the over current indicator.

We would like to move these drivers to use a regulator instead, because
it makes the driver generic allowing to use in the future any type of
regulator (maybe i2c based), And also it helps removing some code making
DT migration simpler and avoiding to add new bindings each time.

Vbus control is easy enough as the infrastructure to handle this
is in place using a fixed regulator for the simple gpio case.

Handling of the over current pin, however, needs some modifications
to the regulator framework, to be able to transmit the over current
pin status to the usb driver.

This is an attempt to extend the fixed regulator to handle the over
current pin, and send the status via a notification with minimal
framework changes, avoiding to use get_status which would have to 
be exported to consumers or get_mode which is not supposed to be
used for this purpose.

Axel Haslam (3):
  regulator: core: Add over current changed event
  regulator: fixed: Handle optional overcurrent pin
  regulator: fixed: dt: Allow an optional over current pin

 .../bindings/regulator/fixed-regulator.txt         |  4 ++
 drivers/regulator/fixed.c                          | 55 ++++++++++++++++++++++
 include/linux/regulator/consumer.h                 |  2 +
 include/linux/regulator/fixed.h                    |  3 ++
 4 files changed, 64 insertions(+)

-- 
1.9.1

             reply	other threads:[~2016-10-26 19:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 19:00 ahaslam [this message]
2016-10-26 19:00 ` [RFC 1/3] regulator: core: Add over current changed event ahaslam
2016-10-28 18:22   ` Mark Brown
2016-10-28 19:41     ` Axel Haslam
2016-10-29  8:50       ` Axel Haslam
2016-10-29 18:40       ` Mark Brown
2016-10-30 12:02         ` Axel Haslam
2016-10-31 16:22           ` Mark Brown
2016-11-01 15:47             ` Axel Haslam
2016-10-26 19:00 ` [RFC 2/3] regulator: fixed: Handle optional overcurrent pin ahaslam
2016-10-26 19:00 ` [RFC 3/3] regulator: fixed: dt: Allow an optional over current pin ahaslam

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=20161026190054.11968-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 \
    /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

all inboxes | Powered by JetHome®