From: Matthias Kaehlcke <mka@chromium.org>
To: Rob Herring <robh@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Brian Norris <briannorris@chromium.org>,
Guenter Roeck <groeck@chromium.org>,
Dmitry Torokhov <dtor@chromium.org>
Subject: Re: [PATCH v1] regulator: Add driver for voltage controlled regulators
Date: Mon, 27 Feb 2017 10:53:10 -0800 [thread overview]
Message-ID: <20170227185310.GA153648@google.com> (raw)
In-Reply-To: <20170225031919.GB56005@google.com>
El Fri, Feb 24, 2017 at 07:19:19PM -0800 Matthias Kaehlcke ha dit:
> El Tue, Feb 21, 2017 at 06:22:14PM -0600 Rob Herring ha dit:
> >
> > > +Optional properties:
> > > +--------------------
> > > ...
> > > +- min-slew-down-rate : Describes how slowly the regulator voltage will decay
> > > + down in the worst case (lightest expected load).
> > > + Specified in uV / us (like main regulator ramp rate).
> > > + This value is required when ovp-threshold-percent is
> > > + specified.
> >
> > Don't we have a standard prop for this or that's just for ramp?
>
> regulator-ramp-delay is related, but not exactly the same. The
> ramp-delay is applied at the end of an up- or downward transition,
> while this prop only specifies the downward rate and is applied in
> between partial transitions towards the final voltage.
>
> We possibly could use ramp-delay and add a set_voltage_time() op to
> vctrl to prevent the core code from adding the "normal" ramp-delay at
> the end of the transition. However it could be confusing that vctrl
> handles the ramp-delay differently than other drivers, especially we
> don't want a delay in the upward transition for vctrl. But maybe
> nobody would care about the different behavior, as long as the
> regulator does its job ...
Actually the behavior of a delay on the downward transition and no
delay on the upward transition is hardware specific. Other users of
this driver might need a standard ramp delay, therefore I think it's
not a good idea to (re-)use this property in vctrl.
Matthias
prev parent reply other threads:[~2017-02-28 9:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 20:43 Matthias Kaehlcke
2017-02-11 0:32 ` Matthias Kaehlcke
2017-02-22 0:22 ` Rob Herring
2017-02-25 3:19 ` Matthias Kaehlcke
2017-02-27 18:53 ` Matthias Kaehlcke [this message]
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=20170227185310.GA153648@google.com \
--to=mka@chromium.org \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dtor@chromium.org \
--cc=groeck@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@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
Powered by JetHome