Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1444282
| From | Mark Brown <broonie@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: "coupled" regulator support |
| Date | 2016-07-15 15:00 +0200 |
| Message-ID | <rVaSL-70X-31@gated-at.bofh.it> (permalink) |
| References | <rVa6l-6K7-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Fri, Jul 15, 2016 at 08:01:13PM +0800, Jisheng Zhang wrote: > regR can only be set to v1 if devA and devB all call for set voltage to v1 > regR can set to v2 if devA or devB call for set voltage to v2 > To support this situation, I'd like to add flag to regulator structure and > patch regulator_check_consumers() to check whether we are safe to set the vol Surely this is just what normal set voltage calls do? If devA says set_voltage(v1, v2) but devB still has set_voltage(v2, v2) then we will leave the voltage at v2, we'll only allow it to be set to v1 if both consumers agree that this is a valid voltage. It feels like there's something else going on here that I'm missing?
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
"coupled" regulator support Jisheng Zhang <jszhang@marvell.com> - 2016-07-15 14:10 +0200
Re: "coupled" regulator support Mark Brown <broonie@kernel.org> - 2016-07-15 15:00 +0200
Re: "coupled" regulator support Jisheng Zhang <jszhang@marvell.com> - 2016-07-18 08:50 +0200
Re: "coupled" regulator support Mark Brown <broonie@kernel.org> - 2016-07-18 20:10 +0200
Re: "coupled" regulator support Jisheng Zhang <jszhang@marvell.com> - 2016-07-21 13:00 +0200
csiph-web