Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1637865
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property |
| Date | 2017-05-09 07:30 +0200 |
| Message-ID | <tF5SF-5H8-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <tAsPV-197-35@gated-at.bofh.it> <tBkZY-4ij-13@gated-at.bofh.it> <tD0Ns-4I5-3@gated-at.bofh.it> <tEL7A-P9-21@gated-at.bofh.it> <tERmG-4Cr-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 08-05-17, 14:57, Sudeep Holla wrote: > Yes, I followed the thread and figured that out. But Rajendra also > raised "What if the microcontroller firmware maps the performance-index > to voltage but expects linux to scale the frequency? There is no way to > specify a performance-index *and* a frequency for a OPP now I guess? So > this needs to be addressd now IIUC. No, he misunderstood it. He was saying that the domain needs a performance-index and the device needs freq-scaling, how do we do that? He thought that there will be just one OPP table for the device here, but we will actually have two and that would work. > So as Kevin pointed out, we need to experiment and look at all > possibilities before finalizing the bindings. Better to have examples > for all these and describe how bindings are be used including how to > distinguish between these use-case from the bindings if it's not implicit. Yeah, I have some doubts on how we are going to implement that and looking for more input from him. -- viresh
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH V6 0/9] PM / Domains: Implement domain performance states Viresh Kumar <viresh.kumar@linaro.org> - 2017-04-26 13:00 +0200
[PATCH V6 8/9] PM / Domain: Add struct device to genpd Viresh Kumar <viresh.kumar@linaro.org> - 2017-04-26 13:00 +0200
[PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Viresh Kumar <viresh.kumar@linaro.org> - 2017-04-26 13:00 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Rob Herring <robh@kernel.org> - 2017-04-28 22:50 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Sudeep Holla <sudeep.holla@arm.com> - 2017-05-03 13:40 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Kevin Hilman <khilman@baylibre.com> - 2017-05-06 23:50 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Sudeep Holla <sudeep.holla@arm.com> - 2017-05-08 15:50 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Viresh Kumar <viresh.kumar@linaro.org> - 2017-05-08 09:20 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Sudeep Holla <sudeep.holla@arm.com> - 2017-05-08 16:00 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Viresh Kumar <viresh.kumar@linaro.org> - 2017-05-09 07:30 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Kevin Hilman <khilman@baylibre.com> - 2017-05-06 23:50 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Viresh Kumar <viresh.kumar@linaro.org> - 2017-05-08 06:20 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Rajendra Nayak <rnayak@codeaurora.org> - 2017-05-08 07:40 +0200
Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property Viresh Kumar <viresh.kumar@linaro.org> - 2017-05-08 09:20 +0200
[PATCH V6 7/9] PM / domain: Register PM QOS performance notifier Viresh Kumar <viresh.kumar@linaro.org> - 2017-04-26 13:00 +0200
[PATCH V6 5/9] PM / OPP: Add support to parse "power-domain-opp" property Viresh Kumar <viresh.kumar@linaro.org> - 2017-04-26 13:00 +0200
csiph-web