[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161024181937.GP17252@sirena.org.uk>
Date: Mon, 24 Oct 2016 19:19:37 +0100
From: Mark Brown <broonie@...nel.org>
To: Axel Haslam <ahaslam@...libre.com>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Johan Hovold <johan@...nel.org>, robh+dt@...nel.org,
Sekhar Nori <nsekhar@...com>,
Alan Stern <stern@...land.harvard.edu>,
Kevin Hilman <khilman@...libre.com>,
Sergei Shtylyov <sshtylyov@...mvista.com>,
David Lechner <david@...hnology.com>,
manjunath.goudar@...aro.org,
Alexandre Bailon <abailon@...libre.com>,
linux-usb@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH/RFT v2 09/17] regulator: fixed: Add over current event
On Mon, Oct 24, 2016 at 08:11:40PM +0200, Axel Haslam wrote:
> On Mon, Oct 24, 2016 at 7:53 PM, Mark Brown <broonie@...nel.org> wrote:
> > does it make sense to report this as a mode, we don't report other error
> > conditions as modes but instead use REGULATOR_STATUS_ with the
> > get_status() operation?
> I used mode, because when the regulator toggles the overcurrent
> line, it means that it has entered a current limited mode, at least the
> regulator im looking at. ill change to STATUS
That's not what regulator modes are - please look at the documentation
for the defines here. They're about the quality of regulation.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists