public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "broonie@kernel.org" <broonie@kernel.org>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>,
	"rob@landley.net" <rob@landley.net>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Subject: Re: [PATCH V2] regulator: core: add support for configuring turn-on time through constraints
Date: Wed, 11 Sep 2013 23:39:18 +0530	[thread overview]
Message-ID: <5230B1CE.3090709@nvidia.com> (raw)
In-Reply-To: <5230AC61.30904@wwwdotorg.org>

On Wednesday 11 September 2013 11:16 PM, Stephen Warren wrote:
> On 09/11/2013 11:46 AM, Laxman Dewangan wrote:
>> On Wednesday 11 September 2013 10:47 PM, Stephen Warren wrote:
>>> - regulator-enable-ramp-delay: The time taken, in uSec, for the supply
>>> rail to reach the target voltage, plus/minus whatever tolerance the
>>> board design requires, once the regulator output itself has ramped up.
>>> This value is in addition to whatever built-in ramp time is inherent in
>>> the regulator's own internal design or configuration. This property
>>> describes the additional ramp time required due to board design issues
>>> such as trace capacitance and load on the supply.
>>>
>>> That's text repeats "additional" a bit, but I think describes the
>>> situation correctly?
>> I wanted to provide the absolute delay rather than additional delay on
>> top of inherit delay from device.
> I suppose that either is fine from a DT perspective. But, the regulator
> drivers already know their internal delay, so presumably driver code
> will have to take the value from DT, and subtract out whatever delay the
> driver already embodies, in order to calculate the extra delay required?
> Or, if this property is set, does the driver-specified delay just get
> ignored?

Yes, if property is available then driver-specified delay get ignored. 
Delay will be used from dt provided value.

Thanks,
Laxman



  reply	other threads:[~2013-09-11 17:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 12:58 [PATCH V2] regulator: core: add support for configuring turn-on time through constraints Laxman Dewangan
2013-09-11 17:17 ` Stephen Warren
2013-09-11 17:46   ` Laxman Dewangan
2013-09-11 17:46     ` Stephen Warren
2013-09-11 18:09       ` Laxman Dewangan [this message]
2013-09-11 17:59         ` Stephen Warren
2013-09-12 10:12           ` Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5230B1CE.3090709@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=swarren@wwwdotorg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox