Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1524984
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support |
| Date | 2016-11-18 04:10 +0100 |
| Message-ID | <sEHIR-1j0-5@gated-at.bofh.it> (permalink) |
| References | <swq2t-8jC-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 26-10-16, 12:02, Viresh Kumar wrote: > Hi, > > Some platforms (like TI) have complex DVFS configuration for CPU > devices, where multiple regulators are required to be configured to > change DVFS state of the device. This was explained well by Nishanth > earlier [1]. > > One of the major complaints around multiple regulators case was that the > DT isn't responsible in any way to represent the ordering in which > multiple supplies need to be programmed, before or after frequency > change. It was considered in this patch and such information is left to > the platform specific OPP driver now, which can register its own > opp_set_rate() callback with the OPP core and the OPP core will then > call it during DVFS. > > The patches are tested on Exynos5250 (Dual A15). I have hacked around DT > and code to pass values for multiple regulators and verified that they > are all properly read by the kernel (using debugfs interface). > > Dave Gerlach has already tested it on the real TI platforms and it works > well for him. > > This is rebased over: linux-next branch in the PM tree. > > V2->V3: > - The last patch is new > - Removed a debug leftover pr_info() message > - Renamed few names as s/set_rate/set_opp > - Removed a TODO comment (as it is done now with this series) > - created struct for min_uV and max_uV > - kerneldoc comments for structures in pm_opp.h > - s/const char */const char * const > - use kasprintf() > - Some more minor reformatting > - More Ack/RBY tags added Hi guys, Can we please get this series reviewed quickly and come to a conclusion? It has already taken a lot of time getting this merged and the present code seems to be the best possible shot we have, AFAIU. -- viresh
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-18 04:10 +0100
Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support Mark Brown <broonie@kernel.org> - 2016-11-18 11:50 +0100
Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-22 04:50 +0100
Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support Mark Brown <broonie@kernel.org> - 2016-11-22 19:50 +0100
Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-23 05:00 +0100
Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support Mark Brown <broonie@kernel.org> - 2016-11-23 13:40 +0100
Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-24 06:10 +0100
Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support Mark Brown <broonie@kernel.org> - 2016-11-24 11:20 +0100
csiph-web