Menon, Nishanth n...@ti.com writes:
On Tue, Jun 7, 2011 at 16:49, Kevin Hilman khil...@ti.com wrote:
Nishanth Menon n...@ti.com writes:
Since we do module_init, cpufreq initializes before power late_init
where many of the required data structures are registered.
What exactly are the
On Wed, Jun 8, 2011 at 13:51, Kevin Hilman khil...@ti.com wrote:
[..]
the issue is as follows:
currently we dont do voltage transitions. when we do that
eventually(and my current code has an forked implementation of dvfs,
the following steps happen):
late_initcall(omap2_common_pm_late_init);
Menon, Nishanth n...@ti.com writes:
On Wed, Jun 8, 2011 at 13:51, Kevin Hilman khil...@ti.com wrote:
[..]
the issue is as follows:
currently we dont do voltage transitions. when we do that
eventually(and my current code has an forked implementation of dvfs,
the following steps happen):
On 6/7/2011 7:35 AM, Nishanth Menon wrote:
Since we do module_init, cpufreq initializes before power late_init
where many of the required data structures are registered. Move
cpufreq init to late_initcall instead. Further CONFIG_CPU_FREQ
on which the build depends is bool and does'nt support
On Tue, Jun 7, 2011 at 03:15, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
On 6/7/2011 7:35 AM, Nishanth Menon wrote:
Since we do module_init, cpufreq initializes before power late_init
where many of the required data structures are registered. Move
cpufreq init to late_initcall instead.
Nishanth Menon n...@ti.com writes:
Since we do module_init, cpufreq initializes before power late_init
where many of the required data structures are registered.
What exactly are the dependencies here? The only thing I see is the
dependency on omap2_get_mpuss_device(), and those devices
On Tue, Jun 7, 2011 at 16:49, Kevin Hilman khil...@ti.com wrote:
Nishanth Menon n...@ti.com writes:
Since we do module_init, cpufreq initializes before power late_init
where many of the required data structures are registered.
What exactly are the dependencies here? The only thing I see is
Since we do module_init, cpufreq initializes before power late_init
where many of the required data structures are registered. Move
cpufreq init to late_initcall instead. Further CONFIG_CPU_FREQ
on which the build depends is bool and does'nt support modules yet.
Signed-off-by: Nishanth Menon
