But the system is woken by the known source, BT wakeup configures the UART2
CTS pad config for wakeup.


On Sun, Nov 29, 2009 at 3:27 PM, <neo.driz...@gmail.com> wrote:

> This looks like android behavior ...once the system suspend is woken by
> known wakup source, the userland would triger late resume. If not late
> resume won't be called.
> You will see the same behavior if you press any random key other then
> specified wakup keys.
>
> -girish
>
>
> On Nov 26, 2009, at 12:46 PM, BHEEMSEN KULKARNI <bheems...@gmail.com>
> wrote:
>
> Hi,
> We have a question regarding the LCD wake up due to external BT pairing
> request.
>
>
> When Android goes to suspend and BT chips goes to sleep, if we try to pair
> from remote device, OMAP core wakes due to UART2 CTS (UART2 CTS configured
> as BT wakeup source). But LCD is not coming up with pin request.
>
>
>
>  Please let us know what is the expected behavior in this scenario?
>
>
>
> Shouldn’t the application turn on the LCD and show the pin request?
>
>
> Note: Above behavior observed in kernel 2.6.29 and donut file system.
>
> Thanks in advance
>
> Thanks and Regards
> Bheemsen
>
> --
> unsubscribe: <android-porting+unsubscr...@googlegroups.com>
> android-porting+unsubscr...@googlegroups.com
> website: <http://groups.google.com/group/android-porting>
> http://groups.google.com/group/android-porting
>
>  --
> unsubscribe: 
> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com>
> website: http://groups.google.com/group/android-porting

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to