On Tue, Oct 4, 2011 at 5:44 PM, Paolo Pisati <email address hidden> wrote:
> On 10/04/2011 10:58 AM, Ming Lei wrote:
>>
>> Not mention before, RTC can wakeup system certainly.
>
> yep, last time i tried rtc correctly generated the interrupt when the
> timer expired but it didn't wake up the board
>
>>> can you point me to the patches you tried on top of mainline?
>>
>> It is the patch set written by Govindraj.R" <email address hidden>:
>>
>> OMAP2+: UART: Add runtime pm support for omap-serial driver
>
> ok, i'll take a look
In fact, 3.1-rc6 can be woke up by uart2 without any patch after you
enabled remote wakeup for ttyO2.
But looks like there are still some problems about ubuntu oneiric omap4 kernel:
- musb suspend oos
- some other warnings in suspend path
......
On Tue, Oct 4, 2011 at 5:44 PM, Paolo Pisati <email address hidden> wrote:
> On 10/04/2011 10:58 AM, Ming Lei wrote:
>>
>> Not mention before, RTC can wakeup system certainly.
>
> yep, last time i tried rtc correctly generated the interrupt when the
> timer expired but it didn't wake up the board
>
>>> can you point me to the patches you tried on top of mainline?
>>
>> It is the patch set written by Govindraj.R" <email address hidden>:
>>
>> OMAP2+: UART: Add runtime pm support for omap-serial driver
>
> ok, i'll take a look
In fact, 3.1-rc6 can be woke up by uart2 without any patch after you
enabled remote wakeup for ttyO2.
But looks like there are still some problems about ubuntu oneiric omap4 kernel:
- musb suspend oos
- some other warnings in suspend path
......
thanks,
--
Ming Lei