Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1034107AbcJ1SgT (ORCPT ); Fri, 28 Oct 2016 14:36:19 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:46680 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966057AbcJ1Sfy (ORCPT ); Fri, 28 Oct 2016 14:35:54 -0400 Date: Fri, 28 Oct 2016 19:22:50 +0100 From: Mark Brown To: ahaslam@baylibre.com Cc: lgirdwood@gmail.com, khilman@baylibre.com, nsekhar@ti.com, david@lechnology.com, linux-kernel@vger.kernel.org Message-ID: <20161028182250.df6p6setaauxsezu@sirena.org.uk> References: <20161026190054.11968-1-ahaslam@baylibre.com> <20161026190054.11968-2-ahaslam@baylibre.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="za6chuaylf3ydazw" Content-Disposition: inline In-Reply-To: <20161026190054.11968-2-ahaslam@baylibre.com> X-Cookie: Serenity through viciousness. User-Agent: NeoMutt/20161014 (1.7.1) X-SA-Exim-Connect-IP: 64.88.227.140 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [RFC 1/3] regulator: core: Add over current changed event X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1540 Lines: 39 --za6chuaylf3ydazw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 26, 2016 at 09:00:52PM +0200, ahaslam@baylibre.com wrote: > From: Axel Haslam >=20 > Regulator consumers may be interested to know when the > over current condition is over. >=20 > 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. --za6chuaylf3ydazw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAABCAAGBQJYE5d5AAoJECTWi3JdVIfQHqUH+wXoBUmTtVg+Nh1uUW+ZrNds 1XPQA3nALWT4470BFfY9RdS0hgdz0P/o9w8r6rgOe9I3hxMsHKhhzGrm54Bz1wV5 sE5teouyZxifla1fctOXGFqy54unIv/DyRISnVH7gnAit7v+KDwlsvHN+gZmLiJp 7vZhNL1lt6i9Bi6YPdqtQsfNuW6F3fB5opQ2/S7/EFt11Unyk+oIxo0JSPmeoq7o kULjZlxXrQdqNn3ZhnpWSs0wptQ/wvg42APlKltgQaO6c4C5rUGi4ZSZbe7NT7g4 KMQfCI2oVrglhZgw+D/4uh0S8oddIqJqwSVUU18o1CAP0NrX7huhTgWCxxeDbTk= =4H+5 -----END PGP SIGNATURE----- --za6chuaylf3ydazw--