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@kryo.se>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Liam Girdwood <lgirdwood@gmail.com>,
	"Bjorn Andersson" <bjorn.andersson@sonymobile.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@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: Thu, 31 Mar 2016 22:43:03 +0530	[thread overview]
Message-ID: <56FD5A9F.5050001@nvidia.com> (raw)
In-Reply-To: <20160331165145.GF2350@sirena.org.uk>


On Thursday 31 March 2016 10:21 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Thu, Mar 31, 2016 at 12:36:08PM +0530, Laxman Dewangan wrote:
>> On Wednesday 30 March 2016 11:46 PM, Mark Brown wrote:
>>>> Like to add property as "regulator-device-ramp-delay" which will be used for
>>>> PMIC configuration and regulator-ramp-delay will be used for delay
>>>> calculation. This is case when advertised ramp delay does not match with the
>>>> platform measured ramp delay.
>>> Why -device?
>> This is device specific and just to differentiate with regulator-ramp-delay
>> which is the platform specific.
>> May be there is some other good name. I can think of other name as
>> regulator-typical-ramp-delay, regulator-advertised-ramp-delay etc.
> So there's already a property you want to set, why are you not trying to
> set that property?

We need two properties, one what we measured in platform and second one 
for what we want to program PMIC. This is for the case where vendor 
advertised ramp delay is not same as measured due to platform design.
Based on discussion, regulator-ramp-delay is for measured ramp delay in 
platform. So we will need another property for configuring PMIC.

WARNING: multiple messages have this Message-ID (diff)
From: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Bjorn Andersson <bjorn-UYDU3/A3LUY@public.gmane.org>,
	Bjorn Andersson
	<bjorn.andersson-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Pawel Moll <pawel.moll-5wv7dgnIgG8@public.gmane.org>,
	Mark Rutland <mark.rutland-5wv7dgnIgG8@public.gmane.org>,
	Ian Campbell
	<ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	Liam Girdwood <lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Bjorn Andersson
	<bjorn.andersson-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org>,
	Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>,
	"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Gandhar Dighe <gdighe-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
	Stuart Yates <syates-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH 1/2] regulator: DT: Add support to scale ramp delay based on platform behavior
Date: Thu, 31 Mar 2016 22:43:03 +0530	[thread overview]
Message-ID: <56FD5A9F.5050001@nvidia.com> (raw)
In-Reply-To: <20160331165145.GF2350-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>


On Thursday 31 March 2016 10:21 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Thu, Mar 31, 2016 at 12:36:08PM +0530, Laxman Dewangan wrote:
>> On Wednesday 30 March 2016 11:46 PM, Mark Brown wrote:
>>>> Like to add property as "regulator-device-ramp-delay" which will be used for
>>>> PMIC configuration and regulator-ramp-delay will be used for delay
>>>> calculation. This is case when advertised ramp delay does not match with the
>>>> platform measured ramp delay.
>>> Why -device?
>> This is device specific and just to differentiate with regulator-ramp-delay
>> which is the platform specific.
>> May be there is some other good name. I can think of other name as
>> regulator-typical-ramp-delay, regulator-advertised-ramp-delay etc.
> So there's already a property you want to set, why are you not trying to
> set that property?

We need two properties, one what we measured in platform and second one 
for what we want to program PMIC. This is for the case where vendor 
advertised ramp delay is not same as measured due to platform design.
Based on discussion, regulator-ramp-delay is for measured ramp delay in 
platform. So we will need another property for configuring PMIC.


--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-03-31 17:23 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
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 [this message]
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=56FD5A9F.5050001@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=bjorn.andersson@sonymobile.com \
    --cc=bjorn@kryo.se \
    --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.