Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1262871
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH V2 2/5] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding |
| Date | 2015-11-05 04:20 +0100 |
| Message-ID | <qrjfI-16l-7@gated-at.bofh.it> (permalink) |
| References | <qrhQB-8ni-9@gated-at.bofh.it> <qrhQB-8ni-7@gated-at.bofh.it> <qrj62-Vz-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 04-11-15, 21:02, Rob Herring wrote: > > +- turbo-mode-<name>: Named turbo-mode property. Similar to opp-microvolt-<name> > > + property, but for turbo mode instead. > > + > > - opp-suspend: Marks the OPP to be used during device suspend. Only one OPP in > > the table should have this. > > > > +- opp-suspend-<name>: Named opp-suspend property. Similar to > > + opp-microvolt-<name> property, but for suspend opp instead. > > + > > I don't think these last 2 make sense. turbo-mode is a flag that the > mode has restrictions such as other cores have to be idle or something. > Similarly, opp-suspend should not vary by <name>. Based on what version of the hardware you are running, via opp-supported-hw property, the platform can enable a different set of OPPs. And in that case we may want to select different OPPs marked as turbo or suspend freq. That's what I thought at least. For example, on version A of the hardware we have following available frequencies: 800, 1000, 1100, 1200 MHz. Where 800 MHz is the suspend freq and 1200 is the turbo one. But on a slightly different version of hardware B, we have two more OPPs available: 700 and 1400 MHz. And in that case we want the suspend freq to be 700 and turbo OPP to be only 1400 MHz. -- viresh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH V2 2/5] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-11-05 02:50 +0100
Re: [PATCH V2 2/5] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding Rob Herring <robh@kernel.org> - 2015-11-05 04:10 +0100
Re: [PATCH V2 2/5] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-11-05 04:20 +0100
Re: [PATCH V2 2/5] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding Rob Herring <robh@kernel.org> - 2015-11-06 00:40 +0100
Re: [PATCH V2 2/5] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-11-06 03:00 +0100
Re: [PATCH V2 2/5] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding Viresh Kumar <viresh.kumar@linaro.org> - 2015-11-10 16:00 +0100
Re: [PATCH V2 2/5] PM / OPP: Add {opp-microvolt|opp-microamp|turbo-mode|opp-suspend}-<name> binding Rob Herring <robh@kernel.org> - 2015-11-10 16:40 +0100
csiph-web