On Tue, May 15, 2012 at 8:10 PM, Cousson, Benoit wrote:
> Hi Jon,
>
>
> On 5/15/2012 4:33 PM, Jon Hunter wrote:
>>
>> Hi Santosh, Benoit,
>>
>> On 05/10/2012 01:54 AM, Santosh Shilimkar wrote:
>>>
>>> On Thursday 10 May 2012 03:06 AM, Jon Hunter wrote:
From: Jon Hunter
For OMAP
Hi Jon,
On 5/15/2012 4:33 PM, Jon Hunter wrote:
Hi Santosh, Benoit,
On 05/10/2012 01:54 AM, Santosh Shilimkar wrote:
On Thursday 10 May 2012 03:06 AM, Jon Hunter wrote:
From: Jon Hunter
For OMAP3+ devices, the clock domains (CLKDMs) support one or more of the
following transition modes ...
Hi Santosh, Benoit,
On 05/10/2012 01:54 AM, Santosh Shilimkar wrote:
> On Thursday 10 May 2012 03:06 AM, Jon Hunter wrote:
>> From: Jon Hunter
>>
>> For OMAP3+ devices, the clock domains (CLKDMs) support one or more of the
>> following transition modes ...
>>
>> NO_SLEEP (0x0) - A clock domain sl
On Thursday 10 May 2012 03:06 AM, Jon Hunter wrote:
> From: Jon Hunter
>
> For OMAP3+ devices, the clock domains (CLKDMs) support one or more of the
> following transition modes ...
>
> NO_SLEEP (0x0) - A clock domain sleep transition is never initiated,
>irrespective of the hard
From: Jon Hunter
For OMAP3+ devices, the clock domains (CLKDMs) support one or more of the
following transition modes ...
NO_SLEEP (0x0) - A clock domain sleep transition is never initiated,
irrespective of the hardware conditions.
SW_SLEEP (0x1) - A software-forced sleep transi
