From: Matthias Kaehlcke <mka@chromium.org>
To: Mark Brown <broonie@kernel.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@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>
Subject: Re: [PATCH] regulator: Allow for asymmetric settling times
Date: Mon, 1 May 2017 09:42:27 -0700 [thread overview]
Message-ID: <20170501164227.GU128305@google.com> (raw)
In-Reply-To: <20170430123001.iwauodtjkbnmjmsl@sirena.org.uk>
Hi Mark and Laxman,
thanks for your comments.
El Sun, Apr 30, 2017 at 09:30:01PM +0900 Mark Brown ha dit:
> On Sat, Apr 29, 2017 at 01:32:09PM +0530, Laxman Dewangan wrote:
> > On Saturday 29 April 2017 05:36 AM, Matthias Kaehlcke wrote:
>
> > > -- regulator-settling-time-us: Settling time, in microseconds, for voltage
> > > - change if regulator have the constant time for any level voltage change.
> > > - This is useful when regulator have exponential voltage change.
> > > +- regulator-settling-time-up-us: Settling time, in microseconds, for voltage
> > > + increase if the regulator needs a constant time to settle after voltage
> > > + increases of any level. This is useful for regulators with exponential
> > > + voltage changes.
> > > +- regulator-settling-time-down-us: Settling time, in microseconds, for voltage
> > > + decrease if the regulator needs a constant time to settle after voltage
> > > + decreases of any level. This is useful for regulators with exponential
> > > + voltage changes.
>
> > Can we have regulator-settling-time-us also so if it is there then up/down
> > same.
> > If up/down different then separate properties can be used.
>
> Removing the existing binding would also break existing DTs using it
> which we obviously don't want.
I thought it might be ok in this case since the driver just landed.
> I don't see any reason to even deprecate it, like Laxman says it's
> nice and convenient for people with symmetric performance.
Ok, I was 'concerned' about the redundancy, but if that is not seen as
an issue I'm happy to just add the new properties. I'll send an
updated patch soon.
Thanks
Matthias
prev parent reply other threads:[~2017-05-01 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 0:06 [PATCH] regulator: Allow for asymmetric settling times Matthias Kaehlcke
2017-04-29 8:02 ` Laxman Dewangan
2017-04-30 12:30 ` Mark Brown
2017-05-01 16:42 ` 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=20170501164227.GU128305@google.com \
--to=mka@chromium.org \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=ldewangan@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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