On 31/07/13 15:46, Nishanth Menon wrote: > On 07/31/2013 06:14 AM, Sudeep KarkadaNagesha wrote: >> On 30/07/13 21:48, Nishanth Menon wrote: [...] >>> This should setup stage for many of the work we have been trying to >>> figure out on AM/OMAP and few other processors which has to depend on >>> few sets of OPPs which may not be supported on various platforms. >>> >> I still don't get the point why you would publish some OPP in the DT >> when the hardware which it describes doesn't support it. >> >> This may be already discussed when DT support was added to OPP library, >> IMO if for some reason the firmware/boot entity disables some of the >> OPPs, then it can append OPPs in DT with the state(enabled/disabled). >> But this needs extension of current binding. > > you could also have reduced OPP set which needs to be invoked, appending > wont really work if cpufreq table is built as part of probe - it kind of > creates all kind of races which I would really like to avoid. > IIUC opp_set_availability(opp_enable/opp_disable) is designed for such use-case ? Currently there are no users of this API but I see it fits your use case. Even with multiple OPP sets listed in DT as you described, you need to read those fuses and chose the right set of OPPs. Instead you can use opp_en(/dis)able methods to do that ? Regards, Sudeep -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
