Re: [PATCH] regulator: Support ramp-up delay for drivers with get_voltage()

From	Mark Brown <broonie@kernel.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH] regulator: Support ramp-up delay for drivers with get_voltage()
Date	2016-03-30 22:50 +0200
Message-ID	<rivdU-2oS-1@gated-at.bofh.it> (permalink)
References	<ripia-6GA-19@gated-at.bofh.it> <risg3-jV-23@gated-at.bofh.it> <risSK-OW-13@gated-at.bofh.it> <ritc6-113-13@gated-at.bofh.it> <rivdU-2oS-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Wed, Mar 30, 2016 at 12:34:26PM -0700, Stephen Boyd wrote:

> Ok. Just curious, why is there a 'selector' argument to the
> set_voltage() op then? The qcom spmi driver is using that to allow the
> list operation to return the voltage that was actually set. Is that a
> 'selector' interface? We could just as easily have read the hardware to
> figure out the voltage, but I think we implement the list op to avoid
> reading hardware when we know what selector has been chosen during
> voltage changes.

Historical reasons - this predates having the split selector and map
operations.

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH] regulator: Support ramp-up delay for drivers with get_voltage() Georgi Djakov <georgi.djakov@linaro.org> - 2016-03-30 16:30 +0200
  Re: [PATCH] regulator: Support ramp-up delay for drivers with  get_voltage() Mark Brown <broonie@kernel.org> - 2016-03-30 19:40 +0200
    Re: [PATCH] regulator: Support ramp-up delay for drivers with get_voltage() Stephen Boyd <stephen.boyd@linaro.org> - 2016-03-30 20:20 +0200
      Re: [PATCH] regulator: Support ramp-up delay for drivers with  get_voltage() Mark Brown <broonie@kernel.org> - 2016-03-30 20:40 +0200
        Re: [PATCH] regulator: Support ramp-up delay for drivers with  get_voltage() Mark Brown <broonie@kernel.org> - 2016-03-30 22:50 +0200

csiph-web