1,, SUSE Labs,, ,, ‹#› Sometimes it is good to be sleepy Pavel Machek, SUSE Labs

2,, SUSE Labs,, ,, ‹#› EnergySTAR Mandates sleep after 30 minutes of inactivity, by default Common implementations sleep machine after keyboard/mouse inactivity...do some hacks with interrupt activity...do not really work, by design

3,, SUSE Labs,, ,, ‹#› One Laptop Per Child PC style machine...but can suspend/resume in 300msec...and can keep screen and wlan powered while rest of system is sleeping -> good candidate for sleepy linux

4,, SUSE Labs,, ,, ‹#› OpenMoko Mobile phone hardware sleepy is really neccessary there traditionally, hacks are used for this like Motorola „drive me from userland“ stack

5,, SUSE Labs,, ,, ‹#› Notebooks notebook running in a bag is a problem notebook sleeping on the table, when it should be compiling is a problem if you want to be awaken by mp3, obvious thing is sleep 8h; mpg123 alarm.mp3 except that you'll have to listen to the fan whole night and machine will consume 15W instead of 1W

6,, SUSE Labs,, ,, ‹#› Existing interface ( sleep 8h; mpg123 alarm.mp3 ) & echo MAGI > /proc/acpi/wakeup cd /sys/class/rtc/rtc0 echo $(( $(cat since_epoch) + $[7*60* *60] )) > wakealarm nice interface, eh? notice that strings /proc/acpi/wakeup are BIOS defined, and do not seem to be standardized

7,, SUSE Labs,, ,, ‹#› Proposed interface I'd like „sleep 8h; mpg123“ to just work – sleep machine for 8 hours, then wake up and start playing kernel side is non-trivial, but doable demo implementation exists UP only, many features need to be disabled unfortunately, that means that every application that polls something will break sleep lets just fix them

8,, SUSE Labs,, ,, ‹#› Drivers normally, drivers are called in top-down manner to go to sleep sleepy drivers just sleep their hw and tell the rest of kernel „as far as I'm concerned, you can just cut the power to me“

9,, SUSE Labs,, ,, ‹#› Questions? ?