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: Tue, 12 Apr 2016 18:59:06 +0530 [thread overview]
Message-ID: <570CF822.4050002@nvidia.com> (raw)
In-Reply-To: <20160412010226.GO3351@sirena.org.uk>
On Tuesday 12 April 2016 06:32 AM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Tue, Apr 05, 2016 at 01:31:41PM +0530, Laxman Dewangan wrote:
>> On Friday 01 April 2016 09:41 PM, Mark Brown wrote:
>> Now there is not really equation that how it control dV/dt with required
>> current vs regulator's current limit current limit.
> I'm having a hard time tying this in with what you're saying. You're
> saying we have a predictable limit based on some hard maximum inrush
> current but we can't tell what that limit is? What I'd expect is that
> we'd get the spec limit up to some maximum and then cap out at that.
>
>
I have put my understanding based on datasheet and observation but it
seems I am missing some important information which is making difficult
to understand further here.
We are not crossing the maximum limit of the load on the rail per
datasheet. We just changed the output capacitor in the platforms and saw
deviation.
I think I need to go again to Vendor to find out that why changing of
capacitor making the deviation in ramp delay and what is the relation.
Probably, that may help here.
next prev parent reply other threads:[~2016-04-12 13:40 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
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 [this message]
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=570CF822.4050002@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 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.