Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758222AbcJYOdb (ORCPT ); Tue, 25 Oct 2016 10:33:31 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:59998 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755733AbcJYOd3 (ORCPT ); Tue, 25 Oct 2016 10:33:29 -0400 Date: Tue, 25 Oct 2016 15:33:04 +0100 From: Mark Brown To: Axel Haslam Cc: Greg KH , Johan Hovold , robh+dt@kernel.org, Sekhar Nori , Alan Stern , Kevin Hilman , Sergei Shtylyov , David Lechner , manjunath.goudar@linaro.org, Alexandre Bailon , linux-usb@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Message-ID: <20161025143304.GW17252@sirena.org.uk> References: <20161024164634.4330-1-ahaslam@baylibre.com> <20161024164634.4330-10-ahaslam@baylibre.com> <20161024175320.GO17252@sirena.org.uk> <20161024181937.GP17252@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="8EXHJdkEfksMlRxO" Content-Disposition: inline In-Reply-To: X-Cookie: When the cup is full, carry it level. User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 77.103.18.231 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH/RFT v2 09/17] regulator: fixed: Add over current 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: 1496 Lines: 43 --8EXHJdkEfksMlRxO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 25, 2016 at 02:55:48PM +0200, Axel Haslam wrote: > To be able to use regulator to handle the overcurrent pin, i need to be a= ble > to somehow retrieve the over current pin state from the regulator driver. What makes you say that, none of the existing users need this? =20 > As i was trying your suggestion, i remembered why i thought i should use > mode instead of status: Status seems to be for internal regulator driver = use, > there is no regulator_get_status, function and REGULATOR_STATUS_* are def= ined > in driver.h and not in consumer.h as REGULATOR_MODE_* > Would you be ok if i allow consumers to get the status via a new > "regulator_get_status" call? What would they do with this information that they can't do with the existing error notification? --8EXHJdkEfksMlRxO Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJYD20fAAoJECTWi3JdVIfQslUH/RwiAIL6cJZcpSWFNfYQSifW txIthbHCklL6vKPdwWsIkx6GCQ7HcICvpQW7/MHVtB1iCtKXm1TXAjvBVDqhdYJj oUZnkxs1UTKnYcnNR4qy1qxRai/zPo8ioJBmX/helfiqWOBdRmnDmcyUs8hVxGNJ mBz1qUGmebZJKiKaDjdYCllwkJN65007OONmKbELsadXA+hCN5haUsa+7X/5hOnt dA6VVOvhFQGUkeUUS2S0c43dTt0iVDG84cJ2aqtLc1ztCbKzwTTTPv+SVCWBgNzA fS7TE1pD4iaNzJvY0ooliRZ5IiC9m1K+ERBLWvsqQmBT9un606USuyvSzniXp8g= =+nJb -----END PGP SIGNATURE----- --8EXHJdkEfksMlRxO--