Kevin Hilman wrote: > Nishanth Menon <[email protected]> writes: > > > SmartReflex is not quite working with this version which is in > pm-wip-opp. My (untested) theory below... Mostly you have not included SR in the build. OTOH I raised this issue earlier that the omap cpufreq driver is not honoring CPUFREQ_RELATION_L and CPUFREQ_RELATION_H flags. I do not understand why do we need to do a opp_find_freq_ceil here? The validate function of the frequency resources would have already identified if we can get this exact frequency or not. -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
- Re: [PATCH 5/9] omap3: pm: sr: replace get_opp with f... Kevin Hilman
- Re: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Menon, Nishanth
- Re: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Kevin Hilman
- Re: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Nishanth Menon
- Re: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Kevin Hilman
- RE: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Sripathy, Vishwanath
- Re: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Romit Dasgupta
- RE: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Sripathy, Vishwanath
- Re: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Nishanth Menon
- Re: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Nishanth Menon
- Re: [PATCH 5/9] omap3: pm: sr: replace get_opp w... Romit Dasgupta
