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


Groups > linux.kernel > #1509708

[RFC 1/3] regulator: core: Add over current changed event

From ahaslam@baylibre.com
Newsgroups linux.kernel
Subject [RFC 1/3] regulator: core: Add over current changed event
Date 2016-10-26 21:10 +0200
Message-ID <swBKh-809-3@gated-at.bofh.it> (permalink)
References <swBKh-809-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


From: Axel Haslam <ahaslam@baylibre.com>

Regulator consumers may be interested to know when the
over current condition is over.

Add an over currerent "changed" event. The registered useres
for this event can then check the over current flag to know
the status of the over current condition.

Signed-off-by: Axel Haslam <ahaslam@baylibre.com>
---
 include/linux/regulator/consumer.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/regulator/consumer.h b/include/linux/regulator/consumer.h
index 6921082..8e33f72 100644
--- a/include/linux/regulator/consumer.h
+++ b/include/linux/regulator/consumer.h
@@ -103,6 +103,7 @@
  *                      Data passed is old voltage cast to (void *).
  * PRE_DISABLE    Regulator is about to be disabled
  * ABORT_DISABLE  Regulator disable failed for some reason
+ * OVER_CURRENT_CHANGE  Regulator over current condition changed
  *
  * NOTE: These events can be OR'ed together when passed into handler.
  */
@@ -119,6 +120,7 @@
 #define REGULATOR_EVENT_ABORT_VOLTAGE_CHANGE	0x200
 #define REGULATOR_EVENT_PRE_DISABLE		0x400
 #define REGULATOR_EVENT_ABORT_DISABLE		0x800
+#define REGULATOR_EVENT_OVER_CURRENT_CHANGE     0x1000
 
 /**
  * struct pre_voltage_change_data - Data sent with PRE_VOLTAGE_CHANGE event
-- 
1.9.1

Back to linux.kernel | Previous | NextPrevious in thread | 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