[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161024174322.GN17252@sirena.org.uk>
Date: Mon, 24 Oct 2016 18:43:22 +0100
From: Mark Brown <broonie@...nel.org>
To: ahaslam@...libre.com
Cc: gregkh@...uxfoundation.org, johan@...nel.org, robh+dt@...nel.org,
nsekhar@...com, stern@...land.harvard.edu, khilman@...libre.com,
sshtylyov@...mvista.com, david@...hnology.com,
manjunath.goudar@...aro.org, 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 06:46:26PM +0200, ahaslam@...libre.com wrote:
> From: Axel Haslam <ahaslam@...libre.com>
>
> Some regulator supplies have an over-current pin that is
> activated when the hw detects an over current condition.
> When this happens, the hardware enters a current limited
> mode.
Please don't mix random enhancements like this into bigger system
specific RFC serieses, send them separately so they're easier to spot
and there's no confusion with dependencies and then reference them from
the system specific series when you post that.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists