Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1509707

[PATCH 0/3] regulator: Send events on over current condition

Show all headers | View 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

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

[PATCH 0/3] regulator: Send events on over current condition ahaslam@baylibre.com - 2016-10-26 21:10 +0200
  [RFC 1/3] regulator: core: Add over current changed event ahaslam@baylibre.com - 2016-10-26 21:10 +0200
    Re: [RFC 1/3] regulator: core: Add over current changed event Mark Brown <broonie@kernel.org> - 2016-10-28 20:40 +0200
      Re: [RFC 1/3] regulator: core: Add over current changed event Axel Haslam <ahaslam@baylibre.com> - 2016-10-28 21:50 +0200
        Re: [RFC 1/3] regulator: core: Add over current changed event Axel Haslam <ahaslam@baylibre.com> - 2016-10-29 11:00 +0200
        Re: [RFC 1/3] regulator: core: Add over current changed event Mark Brown <broonie@kernel.org> - 2016-10-29 20:50 +0200
          Re: [RFC 1/3] regulator: core: Add over current changed event Axel Haslam <ahaslam@baylibre.com> - 2016-10-30 13:10 +0100
            Re: [RFC 1/3] regulator: core: Add over current changed event Mark Brown <broonie@kernel.org> - 2016-10-31 17:30 +0100
              Re: [RFC 1/3] regulator: core: Add over current changed event Axel Haslam <ahaslam@baylibre.com> - 2016-11-01 16:50 +0100
  [RFC 2/3] regulator: fixed: Handle optional overcurrent pin ahaslam@baylibre.com - 2016-10-26 21:10 +0200

csiph-web