Re: [PATCH] OMAP4: PM: Declare idle modules as functional too

["Cousson, Benoit" <b-cousson@ti.com>]

On 9/24/2010 9:28 AM, Paul Walmsley wrote:
> Hi Rajendra, Partha, Benoît,
>
> On Fri, 24 Sep 2010, Rajendra Nayak wrote:
>
>> The omap4_cm_wait_module_ready function would only check for
>> the modules to be completely functional before declaring them
>> ready to be accessed.
>> There might also be instances where in the module is actually
>> in idle (under h/w control) but should still be declared
>> accessible, as the h/w control would make it functional when
>> needed.
>>
>> Hence make omap4_cm_wait_module_ready return true in case
>> the module is fully functional *or* in idle state.
>> Fail only if the module is fully disabled or stuck intransition.
>>
>> The explaination from the TRM for the idlest bits on OMAP4 is as
>> below for quick reference
>>
>> Module idle state:
>> 0x0 func:     Module is fully functional, including OCP
>> 0x1 trans:    Module is performing transition: wakeup, or sleep, or sleep
>>                abortion
>> 0x2 idle:     Module is in Idle mode (only OCP part). It is functional if
>>                using separate functional clock
>
> Thanks for the detailed changelog.  Do we need to check any other
> registers to ensure that the OCP port is in autoidle, or to ensure that
> the separate functional clock is active?

Unfortunately, we do not have any other status than that in OMAP4 for 
the modules clocks activity :-(

Benoit
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html