From: Mark Brown <broonie@kernel.org>
To: ahaslam@baylibre.com
Cc: lgirdwood@gmail.com, khilman@baylibre.com, nsekhar@ti.com,
david@lechnology.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/3] regulator: core: Add over current changed event
Date: Fri, 28 Oct 2016 19:22:50 +0100 [thread overview]
Message-ID: <20161028182250.df6p6setaauxsezu@sirena.org.uk> (raw)
In-Reply-To: <20161026190054.11968-2-ahaslam@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
On Wed, Oct 26, 2016 at 09:00:52PM +0200, ahaslam@baylibre.com wrote:
> 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.
Would a more general event for error conditions work as well? Thinking
about this I'm unclear how interested consumers are going to be in the
specific error condition as opposed to the fact that the regulator ran
into trouble, and I can imagine that some regulators will report the
same root cause differently - another regulator might detect an
excessive current draw by seeing the output voltage collapse and the
regulator go out of regulation for example.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-10-28 18:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 19:00 [PATCH 0/3] regulator: Send events on over current condition ahaslam
2016-10-26 19:00 ` [RFC 1/3] regulator: core: Add over current changed event ahaslam
2016-10-28 18:22 ` Mark Brown [this message]
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=20161028182250.df6p6setaauxsezu@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ahaslam@baylibre.com \
--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®