From: Mark Brown <broonie@kernel.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: lgirdwood@gmail.com, Douglas Anderson <dianders@chromium.org>,
briannorris@chromium.org, javier@dowhile0.org,
robh+dt@kernel.org, mark.rutland@arm.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 4/4] regulator: Prevent falling too fast
Date: Thu, 15 Sep 2016 15:39:45 +0100 [thread overview]
Message-ID: <20160915143945.GJ27974@sirena.org.uk> (raw)
In-Reply-To: <20160913172140.GC62872@google.com>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Tue, Sep 13, 2016 at 10:21:40AM -0700, Matthias Kaehlcke wrote:
> Optimizing the delay time depends on the SoC; we have not measured
> this across a wide variety of devices and thus have very conservative
> numbers. The percentage is based on the trigger for OVP on the
> regulator. In this case, OVP kicks in when the FB node is 20% over
> regulation, which is equivalent to a 16% drop in voltage (1/1.2). For
> our device safe-fall-percent is set to 16 and slowest-decay-rate is
> 225.
The obvious question here is how the OVP hardware knows about the new
voltage and why we're bodging this in the regulator core rather than in
the OVP hardware.
> > I'd like to see some more thorough analysis than just an "apparently"
> > here. It's making the code more fiddly for something very handwavy.
> It's well-understood why it's a percentage. DVS is controlled by
> offsetting the FB current, and as above, OVP is based on how far you
> are from the FB target.
You might think you understand this clearly but nobody reading the
commit message or looking at the code later on is going to be able
do so when your commit message only contains vague handwaving.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-09-15 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 19:05 Matthias Kaehlcke
2016-09-12 18:56 ` Mark Brown
2016-09-13 17:21 ` Matthias Kaehlcke
2016-09-15 14:39 ` Mark Brown [this message]
2016-09-15 18:02 ` Matthias Kaehlcke
2016-09-16 16:32 ` Mark Brown
2016-09-16 18:31 ` Matthias Kaehlcke
2016-09-16 18:48 ` Mark Brown
2016-09-19 18:39 ` Doug Anderson
2016-09-24 18:41 ` Mark Brown
2016-09-26 17:41 ` Doug Anderson
2016-10-28 18:15 ` Mark Brown
2016-12-12 21:15 ` Matthias Kaehlcke
2016-12-13 17:19 ` Mark Brown
2016-12-13 20:00 ` Doug Anderson
2016-12-13 23:14 ` Matthias Kaehlcke
2016-12-14 13:21 ` 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=20160915143945.GJ27974@sirena.org.uk \
--to=broonie@kernel.org \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=javier@dowhile0.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mka@chromium.org \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®