>>-----Original Message----- >>From: Menon, Nishanth >>Sent: Tuesday, June 08, 2010 9:45 AM >>To: Gopinath, Thara; Kevin Hilman; Nishanth Menon >>Cc: Premi, Sanjeev; Koen Kooi; linux-omap@xxxxxxxxxxxxxxx; eduardo.valentin@xxxxxxxxx >>Subject: opp layer query apis (was RE: omap3 pm: dependency between opp layer and cpufreq) >> >>> -----Original Message----- >>> From: Gopinath, Thara >>> Sent: Friday, June 04, 2010 3:35 PM >>> To: Kevin Hilman; Nishanth Menon >>> Cc: Premi, Sanjeev; Menon, Nishanth; Koen Kooi; linux- >> >> >>> Slightly off the topic but considering we are discussing opp layer here, I >>> do not find API's >>> that take the OPP type (OPP_MPU or OPP_L3) and voltage/frequency as >>> parameters and returns back the associated frequency/voltage. I do not >>> want to get the opp table entry every time I do this. Any chance of >>> introducing this in the framework? I could send a patch for the same. >>Am curios on the usage that combination of >>opp_find_freq_exact >>opp_find_freq_ceil >>opp_find_freq_floor >> >>and opp_get_freq, opp_get_voltage is unable to cater to? Would be interested >>in seeing a patch for the same. Ok here is the need. Let us suppose I know the opp type (OPP_MPU, OPP_L3 ...) etc and the frequency and I need to get the voltage. Today I have to do the following struct omap_opp *opp = opp_find_freq_exact/opp_find_freq_floor/opp_find_freq_ceil(type, freq); u32 volt = opp_get_voltage(opp). As a user of opp layer it would be much simpler for me to do opp_get_volt(type, freq, exact/ceil/floor) as I really do not care about the opp struct at all. Now let us suppose I have the opp type and the voltage I need to put the vdd associated with it to. Today there is no way to retrieve the frequency from the opp layer. Again as a user of the opp layer I would like to have an API u32 freq = opp_get_freq(type, volt) Regards Thara >> >>Regards, >>Nishanth Menon -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html