With CONFIG_PM_RUNTIME disabled, we have a few problems due to the
current way of handling the postsetup_state of each hwmod.
The primary one is that the omap_hwmod internal startup state does not
match the omap_device internal state. For example, with
!CONFIG_PM_RUNTIME, all the hwmods are left enabled (and the bootup
state is OMAP_HWMOD_STATE_ENABLED.)
However, omap_device doesn't know this, so the first call
omap_device_enable() will generate the noisy warnings:
omap_device_enable()
/* Here, the omap_device default state is 0x0: UNKNOWN */
deactivate_func -> omap_device_enable_hwmods()
omap_hwmod_enable()
/* WARN is hit since state is already enabled */
A second one is where device init code is directly calling
omap_hwmod_enable() (e.g. in omap_dm_timer_init_one()). This code has
no way of knowing that the device was left enabled due to the
postsetup_state, so calls like this to omap_hwmod_* fail with the noisy
warnings from the hwmod core.
I haven't dug too much into how to handle this, but wanted to post this
to see if anyone has any good ideas about how to handle it.
Kevin
--
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
