From: Mark Brown <broonie@kernel.org>
To: Stephen Boyd <stephen.boyd@linaro.org>
Cc: Georgi Djakov <georgi.djakov@linaro.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] regulator: Support ramp-up delay for drivers with get_voltage()
Date: Wed, 30 Mar 2016 11:32:07 -0700 [thread overview]
Message-ID: <20160330183207.GR2350@sirena.org.uk> (raw)
In-Reply-To: <20160330181709.5175.51228@sboyd-linaro>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On Wed, Mar 30, 2016 at 11:17:09AM -0700, Stephen Boyd wrote:
> This is for the qcom spmi regulator driver. I seem to have put in the
> set_voltage_time_sel op but missed the fact that the regulator core
> wasn't calling that op to find out how much time to delay. So we have
> raw voltage set and get ops and this selector based delay op.
> Do we need to change the ops to be selector based if we want the
> regulator core to delay after changing voltages? Or do we need to put
> the delay directly into the set_voltage() op in the driver?
You need a consistent set of operations. If you want to use raw
voltages you need to add a raw voltage interface for getting the delay,
not mix selector and non-selector interfaces otherwise we'll run into
problems. It is not sensible to expect a driver that does not use
selectors to implement selectors for some operations, if a driver *does*
use selectors then it should do so consistently. The latter is probably
the more sensible option for this driver since it does have a list
operation so does understand selectors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-30 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 14:23 Georgi Djakov
2016-03-30 17:36 ` Mark Brown
2016-03-30 18:17 ` Stephen Boyd
2016-03-30 18:32 ` Mark Brown [this message]
[not found] ` <20160330193426.5881.34139@sboyd-linaro>
2016-03-30 20:39 ` 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=20160330183207.GR2350@sirena.org.uk \
--to=broonie@kernel.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stephen.boyd@linaro.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®