[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130910163358.GP29403@sirena.org.uk>
Date: Tue, 10 Sep 2013 17:33:58 +0100
From: Mark Brown <broonie@...nel.org>
To: Laxman Dewangan <ldewangan@...dia.com>
Cc: "rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"mark.rutland@....com" <mark.rutland@....com>,
"swarren@...dotorg.org" <swarren@...dotorg.org>,
"rob@...dley.net" <rob@...dley.net>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"lgirdwood@...il.com" <lgirdwood@...il.com>
Subject: Re: [PATCH 2/2] regulator: core: add support for configuring turn-on
time through constraints
On Tue, Sep 10, 2013 at 06:44:40PM +0530, Laxman Dewangan wrote:
> Here my intention for turn-on time is the time from OFF state to ON
> state and the ON voltage settled on this time.
> This time is separate from underlying enable time of the device i.e.
> will not get added.
> We observe in some of platform that some of regulator is taking more
> time than time given as per datasheet.
> Yes, completely agree that this is not the data provided normally,
> just we observe on scope that some of platform shows more than the
> datasheet value and hence this patch.
So, put this in the binding document then! :P This was more a request
to improve the detail in the binding than anything else.
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists