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>,
"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: Fri, 1 Apr 2016 00:01:19 +0530 [thread overview]
Message-ID: <56FD6CF7.5080909@nvidia.com> (raw)
In-Reply-To: <20160331183130.GR2350@sirena.org.uk>
On Friday 01 April 2016 12:01 AM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Thu, Mar 31, 2016 at 11:17:38PM +0530, Laxman Dewangan wrote:
>
>> HW and chip team did simulation with tegra and PMIC and found that the board
>> needs more capacitance then what Vendor recommended for proper signal
>> conditioning on interface. So they put the difference capactitance value and
>> this causes deviation in ramp delay from advertised value. In out design, we
>> measured the ramp time as 50mv/us when PMIC is configured for 100mV/us.
>> So for all settling time, we need to use the ramp as 50mV/us.
>> From DT, I will provide regulator-ramp-delay as 50mv/us.
>> But I do not have property for saying 100mv/us for PMIC configurations and
>> this is what makes need of 2nd property.
> So the PMIC actually has a setting for the rate you're seeing but for
> some resaon you can't use it?
PMIC has the different rate setting what I am seeing on platform (measured).
HW team measured the ramp dealy with specific configuration of rate
setting on PMIC which is not default (OTP-One time programmed from Vendor).
next prev parent reply other threads:[~2016-03-31 18:42 UTC|newest]
Thread overview: 40+ 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 ` [PATCH 2/2] regulator: " Laxman Dewangan
2016-02-29 17:47 ` [PATCH 1/2] regulator: DT: " Bjorn Andersson
2016-03-01 2:23 ` Mark Brown
2016-03-01 3:48 ` Laxman Dewangan
2016-03-02 3:38 ` Mark Brown
2016-03-02 3:35 ` Laxman Dewangan
2016-03-02 4:35 ` Mark Brown
2016-03-02 6:12 ` Laxman Dewangan
2016-03-15 13:41 ` Laxman Dewangan
2016-03-15 14:48 ` Mark Brown
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:47 ` Mark Brown
2016-03-31 17:47 ` Laxman Dewangan
2016-03-31 18:31 ` Mark Brown
2016-03-31 18:31 ` Laxman Dewangan [this message]
2016-03-31 18:45 ` Mark Brown
2016-03-31 18:39 ` Laxman Dewangan
2016-03-31 18:59 ` Mark Brown
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-04-01 7:15 ` Laxman Dewangan
2016-04-01 16:11 ` Mark Brown
2016-04-05 8:01 ` Laxman Dewangan
2016-04-12 1:02 ` Mark Brown
2016-04-12 13:29 ` Laxman Dewangan
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 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=56FD6CF7.5080909@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=bjorn.andersson@linaro.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).