linux-kernel - Re: [RFC 1/3] regulator: core: Add over current changed event

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20161028182250.df6p6setaauxsezu@sirena.org.uk>
Date:   Fri, 28 Oct 2016 19:22:50 +0100
From:   Mark Brown <broonie@...nel.org>
To:     ahaslam@...libre.com
Cc:     lgirdwood@...il.com, khilman@...libre.com, nsekhar@...com,
        david@...hnology.com, linux-kernel@...r.kernel.org
Subject: Re: [RFC 1/3] regulator: core: Add over current changed event

On Wed, Oct 26, 2016 at 09:00:52PM +0200, ahaslam@...libre.com wrote:
> From: Axel Haslam <ahaslam@...libre.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.

Download attachment "signature.asc" of type "application/pgp-signature" (456 bytes)