All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	<robh+dt@kernel.org>, <pawel.moll@arm.com>,
	<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
	<lgirdwood@gmail.com>, <bjorn.andersson@sonymobile.com>,
	<swarren@wwwdotorg.org>, <devicetree@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, Gandhar Dighe <gdighe@nvidia.com>,
	Stuart Yates <syates@nvidia.com>
Subject: Re: [PATCH 1/2] regulator: DT: Add support to scale ramp delay based on platform behavior
Date: Wed, 16 Mar 2016 17:00:49 +0530	[thread overview]
Message-ID: <56E943E9.5020503@nvidia.com> (raw)
In-Reply-To: <20160315144822.GP2566@sirena.org.uk>


On Tuesday 15 March 2016 08:18 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Mar 15, 2016 at 07:11:23PM +0530, Laxman Dewangan wrote:
>
>> So here we will need two parameters:
>> advertised-ramp-delay for PMIC configurations and
>> ramp-delay which is measured one.
>> Most of time, advertised-ramp-delay is same as ramp-delay and hence one
>> value from DT will be sufficient.
>> If there is difference then both value can be provided and
>> advertised-ramp-delay  will be used for PMIC configuration and rest of
>> calculation about delay will be from ramp-delay.
> This sounds more like the difference between typical and maximum spec
> values than anything else, we are looking for maxima in Linux.
>

Maxim datasheet does not say about the typical/maximum. It has only one 
value and that is typical.
However, it has note on the advertised values as:

Note 20.
During a soft-start event or a DVS transition, the regulators output 
current will increase by COUT*dV/dt. In the event that the load current 
plus the additional current imposed by the soft-start or DVS transition, 
reach the regulator’s current limit, the current limit will be enforced. 
When the current limit is enforced, the advertised transition rate 
(dV/dt) will not occur.

WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Mark Brown <broonie@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
	robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, lgirdwood@gmail.com,
	bjorn.andersson@sonymobile.com, swarren@wwwdotorg.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Gandhar Dighe <gdighe@nvidia.com>,
	Stuart Yates <syates@nvidia.com>
Subject: Re: [PATCH 1/2] regulator: DT: Add support to scale ramp delay based on platform behavior
Date: Wed, 16 Mar 2016 17:00:49 +0530	[thread overview]
Message-ID: <56E943E9.5020503@nvidia.com> (raw)
In-Reply-To: <20160315144822.GP2566@sirena.org.uk>


On Tuesday 15 March 2016 08:18 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Mar 15, 2016 at 07:11:23PM +0530, Laxman Dewangan wrote:
>
>> So here we will need two parameters:
>> advertised-ramp-delay for PMIC configurations and
>> ramp-delay which is measured one.
>> Most of time, advertised-ramp-delay is same as ramp-delay and hence one
>> value from DT will be sufficient.
>> If there is difference then both value can be provided and
>> advertised-ramp-delay  will be used for PMIC configuration and rest of
>> calculation about delay will be from ramp-delay.
> This sounds more like the difference between typical and maximum spec
> values than anything else, we are looking for maxima in Linux.
>

Maxim datasheet does not say about the typical/maximum. It has only one 
value and that is typical.
However, it has note on the advertised values as:

Note 20.
During a soft-start event or a DVS transition, the regulators output 
current will increase by COUT*dV/dt. In the event that the load current 
plus the additional current imposed by the soft-start or DVS transition, 
reach the regulator’s current limit, the current limit will be enforced. 
When the current limit is enforced, the advertised transition rate 
(dV/dt) will not occur.

  reply	other threads:[~2016-03-16 11:44 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 14:40 [PATCH 1/2] regulator: DT: Add support to scale ramp delay based on platform behavior Laxman Dewangan
2016-02-29 14:40 ` Laxman Dewangan
2016-02-29 14:40 ` [PATCH 2/2] regulator: " Laxman Dewangan
2016-02-29 14:40   ` Laxman Dewangan
2016-02-29 17:47 ` [PATCH 1/2] regulator: DT: " Bjorn Andersson
2016-02-29 17:47   ` Bjorn Andersson
2016-03-01  2:23   ` Mark Brown
2016-03-01  2:23     ` Mark Brown
2016-03-01  3:48     ` Laxman Dewangan
2016-03-01  3:48       ` Laxman Dewangan
2016-03-02  3:38       ` Mark Brown
2016-03-02  3:38         ` Mark Brown
2016-03-02  3:35         ` Laxman Dewangan
2016-03-02  3:35           ` Laxman Dewangan
2016-03-02  4:35           ` Mark Brown
2016-03-02  4:35             ` Mark Brown
2016-03-02  6:12             ` Laxman Dewangan
2016-03-02  6:12               ` Laxman Dewangan
2016-03-15 13:41             ` Laxman Dewangan
2016-03-15 13:41               ` Laxman Dewangan
2016-03-15 14:48               ` Mark Brown
2016-03-15 14:48                 ` Mark Brown
2016-03-16 11:30                 ` Laxman Dewangan [this message]
2016-03-16 11:30                   ` Laxman Dewangan
2016-03-19  4:31               ` Bjorn Andersson
2016-03-19  8:35                 ` Laxman Dewangan
2016-03-30 13:29                   ` Laxman Dewangan
2016-03-30 18:16                     ` Mark Brown
2016-03-31  7:06                       ` Laxman Dewangan
2016-03-31 16:51                         ` Mark Brown
2016-03-31 17:13                           ` Laxman Dewangan
2016-03-31 17:13                             ` Laxman Dewangan
2016-03-31 17:47                             ` Mark Brown
2016-03-31 17:47                               ` Mark Brown
2016-03-31 17:47                               ` Laxman Dewangan
2016-03-31 17:47                                 ` Laxman Dewangan
2016-03-31 18:31                                 ` Mark Brown
2016-03-31 18:31                                   ` Laxman Dewangan
2016-03-31 18:31                                     ` Laxman Dewangan
2016-03-31 18:45                                     ` Mark Brown
2016-03-31 18:39                                       ` Laxman Dewangan
2016-03-31 18:39                                         ` Laxman Dewangan
2016-03-31 18:59                                         ` Mark Brown
2016-03-31 18:59                                           ` Laxman Dewangan
2016-03-31 18:59                                             ` Laxman Dewangan
2016-03-31 19:22                                             ` Mark Brown
2016-03-31 19:48                                               ` Laxman Dewangan
2016-03-31 20:39                                                 ` Mark Brown
2016-03-31 20:39                                                   ` Mark Brown
2016-04-01  7:15                                                   ` Laxman Dewangan
2016-04-01  7:15                                                     ` Laxman Dewangan
2016-04-01 16:11                                                     ` Mark Brown
2016-04-05  8:01                                                       ` Laxman Dewangan
2016-04-05  8:01                                                         ` Laxman Dewangan
2016-04-12  1:02                                                         ` Mark Brown
2016-04-12  1:02                                                           ` Mark Brown
2016-04-12 13:29                                                           ` Laxman Dewangan
2016-04-13  6:53                                                             ` Mark Brown
2016-04-13  6:53                                                               ` Mark Brown
2016-04-19 10:01                                                               ` Laxman Dewangan
2016-04-19 10:55                                                                 ` Mark Brown
2016-04-19 10:56                                                                   ` Laxman Dewangan
2016-04-19 10:56                                                                     ` Laxman Dewangan
2016-04-19 15:47                                                                     ` 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=56E943E9.5020503@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gdighe@nvidia.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=swarren@wwwdotorg.org \
    --cc=syates@nvidia.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.