Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1604448

Re: [PATCH v2 1/2] regulator: core: add regulator_has_continuous_voltage_range()

From Mark Brown <broonie@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH v2 1/2] regulator: core: add regulator_has_continuous_voltage_range()
Date 2017-03-20 13:10 +0100
Message-ID <tn4im-4vZ-15@gated-at.bofh.it> (permalink)
References <tiQdY-35t-17@gated-at.bofh.it> <tj4qB-4sF-1@gated-at.bofh.it> <tjceu-1g4-25@gated-at.bofh.it> <tm7Lj-4jK-9@gated-at.bofh.it> <tmag9-6m6-1@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 Fri, Mar 17, 2017 at 05:03:30PM -0700, Matthias Kaehlcke wrote:

> In principle I totally agree with you that consumers should be able
> to enumerate the supported voltages with the existing functions. And
> they can, as long as they already know (or assume) that the regulator
> they are using actually has discrete steps, otherwise they might get
> unexpected results.

Given the limits of number representation continuous regulators also
have discrete steps, they just have a lot of them (but so do some
regulators we currently say aren't continuous so...).

> You are right that my case is very specialist, however I think it is
> a general problem that a consumer can't know whether the results of
> _list_voltage(), etc correspond to the regulator itself or to its
> supplies. E.g. a consumer might have a continuous reg which is
> supplied by a discrete reg, in this case _list_voltage() would return
> the steps of the supply reg, which is probably not what most consumers
> expect.

No, this is doesn't make much sense!  Why should we be reporting
properties of the parent regulator when the child regulator is
regulating away all visibility of those properties?

> > > Please see my explication above on why the vctrl driver needs to know
> > > this.

> > I'm seeing nothing in the above that addresses my question, you don't
> > even seem to have mentioned supplies.  

> Sorry, I really didn't try to evade your question. Does it make more
> sense with the example above?

No, not at all.

> > What we should be doing for continuous regulators is allowing people to
> > list the supported voltages as they would for other regulators.

> In the overall regulator context this may make sense, at this point I
> don't really have enough background on the subsystem to have an
> informed opinion.

> From the vctrl perspective I wouldn't be overly happy, since it
> wouldn't allow to distinguish between continuous and discrete
> supplies, and I still think that handling discrete supplies
> differently is simpler/more efficient. This doesn't mean I argue
> against your proposal if it is deemed the right thing from a subsystem
> perspective.

If it helps think of a continuous regulator as a discrete regulator with
a base voltage of 0 and steps of 1uV.

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


Thread

Re: [PATCH v2 1/2] regulator: core: add  regulator_has_continuous_voltage_range() Mark Brown <broonie@kernel.org> - 2017-03-17 22:40 +0100
  Re: [PATCH v2 1/2] regulator: core: add  regulator_has_continuous_voltage_range() Matthias Kaehlcke <mka@chromium.org> - 2017-03-18 01:20 +0100
    Re: [PATCH v2 1/2] regulator: core: add  regulator_has_continuous_voltage_range() Mark Brown <broonie@kernel.org> - 2017-03-20 13:10 +0100
      Re: [PATCH v2 1/2] regulator: core: add  regulator_has_continuous_voltage_range() Matthias Kaehlcke <mka@chromium.org> - 2017-03-23 22:50 +0100
        Re: [PATCH v2 1/2] regulator: core: add  regulator_has_continuous_voltage_range() Mark Brown <broonie@kernel.org> - 2017-03-24 19:50 +0100

csiph-web