linux-kernel - Re: [PATCH 2/2] regulator: core: add support for configuring turn-on time through constraints

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <522F1B40.3040801@nvidia.com>
Date:	Tue, 10 Sep 2013 18:44:40 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Mark Brown <broonie@...nel.org>
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 Tuesday 10 September 2013 05:39 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Sep 10, 2013 at 04:48:08PM +0530, Laxman Dewangan wrote:
>
>> +- regulator-enable-time: Turn ON time for regulator(in uS)
> This is unclear - what is a "turn on time" and is this in addition to or
> separate from the underlying enable time of the device?  It needs to be
> clear that this is the time taken for the voltage to ramp to spec.  I'd
> also expect it to be clear that this is not something that should need
> to be provided normally.

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.

The same rail on other design does not show the enable time more than 
datasheet and on that case, we will not provide this value.



> Please ALSO avoid capitalising words FOR no reason.
>
>
My bad, will take care.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/