Hi, I am using android release 1.0 userland applications with 2.6.25 android kernel. Android works fine with this setup.
Now, the latest kernel is 2.6.28. We have added PM support to it. But we would like to use the same useland file system. (release 1.0) Am are looking into 2 issues now. 1) I have seen that once android goes into PM suspend for the first time. It does not wake up. It remains in suspend even if we get interrupts. Will the 2.6.25 based android kernel (drivers/android/ power.c--> http://pastebin.ca/1313640) PM support work with Android 1.0 userspace? or do i need to change the userspace just because my base kernel version is above 2.6.27? I dont see kernel waking up at all. This happens once in a while. ie calling linux-pm suspend. 2) Most times android does not call Linux-PM which inturn calls device pm. I only get the following android_power: sleep (0->2) at 111463256920 (2000-01-01 00:01:46.651886061 UTC) # android_power: wakeup (2->0) at 140896423418 (2000-01-01 00:02:16.085083076 UTC) android_power_suspend: done I can only see screen blanking only - This is like early suspend. How can i debug and see if something is preventing android from calling linux-pm-suspend (pm_suspend(PM_SUSPEND_MEM); probably wakelocks. But i thought only the new power management framework uses wakelocks. How does one debug this? Can anyone clarify/explain why this happens. Regards, sriram --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel -~----------~----~----~----~------~----~------~--~---
