On Tue, May 24, 2011 at 17:01, Kevin Hilman wrote:
> "Menon, Nishanth" writes:
>
>> On Thu, May 19, 2011 at 08:12, Kevin Hilman wrote:
>>> Nishanth Menon writes:
>>>
OMAP2 does not use OPP tables at the moment for DVFS. Currently,
we depend on opp table initialization to give us the f
"Menon, Nishanth" writes:
> On Thu, May 19, 2011 at 08:12, Kevin Hilman wrote:
>> Nishanth Menon writes:
>>
>>> OMAP2 does not use OPP tables at the moment for DVFS. Currently,
>>> we depend on opp table initialization to give us the freq_table,
>>> which makes sense for OMAP3+. for OMAP2, we s
On Thu, May 19, 2011 at 08:12, Kevin Hilman wrote:
> Nishanth Menon writes:
>
>> OMAP2 does not use OPP tables at the moment for DVFS. Currently,
>> we depend on opp table initialization to give us the freq_table,
>> which makes sense for OMAP3+. for OMAP2, we should be using
>> clk_init_cpufreq_
Nishanth Menon writes:
> OMAP2 does not use OPP tables at the moment for DVFS. Currently,
> we depend on opp table initialization to give us the freq_table,
> which makes sense for OMAP3+. for OMAP2, we should be using
> clk_init_cpufreq_table - so if the opp based frequency table
> initilization
OMAP2 does not use OPP tables at the moment for DVFS. Currently,
we depend on opp table initialization to give us the freq_table,
which makes sense for OMAP3+. for OMAP2, we should be using
clk_init_cpufreq_table - so if the opp based frequency table
initilization fails, fall back to clk_init_cpufr
