I have compiled the kernel using all the required configuration for PM. CONFIG_PM, CONFIG_SUSPEND, CONFIG_WAKELOCK, CONFIG_FB_EARLYSUSPEND, CPU_IDLE etc are set.
After bootup I also see the logs for request_suspend_state() being called. Log : <6>request_suspend_state: wakeup (3->0) at 92533989002 (1970-01-02 00:00:23.984496000 UTC) <3>init: untracked pid 50 exited <3>init: untracked pid 54 exited <6>request_suspend_state: wakeup (0->0) at 142433989002 (1970-01-02 00:01:13.886088000 UTC) So initially on bootup the system moves into PM_SUSPEND_ON state. Regards, Sunil Regards, Sunil On Sep 19, 2:52 pm, 叶祥振 <[email protected]> wrote: > if cat /sys/power/state returns a blank means your kernel do not support > suspend/on state. > I wonder do you have the kernel source, and enable the power managerment > switches in kernel config. > > 2011/9/17 Sunil Pillai <[email protected]> > > > > > > > > > cat /sys/power/wake_lock just prints a blank line. > > Also, cat /sys/power/state returns a blank. > > > Something looks to be seriously wrong. > > > Regards, > > Sunil > > > On Sep 16, 3:55 pm, 叶祥振 <[email protected]> wrote: > > > try to > > > #cat /sys/power/wake_lock > > > and see what's holding the wake lock. > > > Regards > > > > 2011/9/16 Sunil Pillai <[email protected]> > > > > > I tried cat /sys/power/state & it outputs > > > > radio-interface. > > > > > Assuming that the RIL is basically holding a wakelock i tired > > > > debugging using- > > > > echo 15 > /sys/module/wakelock/parameters/debug hoping it to print all > > > > wakelock acuire & release sequences. > > > > This didn't print anything :( > > > > > I hope I'm on track unless has a useful comment at this point! > > > > > Regards, > > > > Sunil > > > > > On Sep 16, 12:31 am, Sunil Pillai <[email protected]> wrote: > > > > > Hello All, > > > > > > I am using android 2.6.35 kernel with a platform using s3c2410 > > > > > processor. After android (gingerbread) boots up the screen as > > expected > > > > > is in the locked state. The screen timeout set is 15 seconds. But > > even > > > > > after long inactivity on the system the screen does not go to > > > > > screen_dim state followed by screen_off state. > > > > > > I tired to move the system to suspend state by writing value "mem" & > > > > > standby into /sys/power/state - > > > > > echo mem > /sys/power/state, but the system does not go to suspend > > > > > state too. (I don't have a dedicated power button to force suspend) > > > > > > I have already enabled early suspend, wakelock etc in "Power > > > > > Management support" section of the config file. > > > > > > Any idea why the LCD backlight doesnot turn off and why the system > > > > > does not react to /sys/power/state interface ? > > > > > > Regards, > > > > > Sunil > > > > > -- > > > > unsubscribe: [email protected] > > > > website:http://groups.google.com/group/android-kernel > > > -- > > unsubscribe: [email protected] > > website:http://groups.google.com/group/android-kernel -- unsubscribe: [email protected] website: http://groups.google.com/group/android-kernel
