Created by Alexander Sack on 2013-05-27 and last modified on 2013-05-27
Get this branch:
bzr branch lp:~asac/powerd/snappy-on-off-with-delayed-suspend-cancellation
Only Alexander Sack can upload to this branch. If you are Alexander Sack please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Alexander Sack

Recent revisions

30. By Alexander Sack on 2013-05-27

only delay suspend requests. activation requests can happen without delay

29. By Alexander Sack on 2013-05-27

allow fast overright of delayed STATE_TRANSITION_NOTIFY events in favour
of more recent state events in check_queued_state_changes; this will ensure
that real suspend gets properly cancelled in case a user event arrives
within NOTIFICATION_TIMEOUT_MSECS after initiating suspend through activity
timeout or power button press

28. By Alexander Sack on 2013-05-27

send state change notification for delayed actions at execution time,
not at scheduling time

27. By Alexander Sack on 2013-05-27

add infrastructure code to cancel delayed state changes and cancel
pending change requests before enqueueing ones

26. By Alexander Sack on 2013-05-27

* refactor how we bridge threads from android input stack thread into
  GMainLoop land; we re-dispatch the android input event wholesale at
  the very first moment to GMainLoop through g_idle_add
  - since this was the only source of multithreading we remove all
    explicit use of mutex in powerd.cpp and power-request.c

25. By Alexander Sack on 2013-05-27

drop a 'sleep(1)' statement from code we never want code like that

24. By Alexander Sack on 2013-05-27

replace usage of 'g_timeout_add(0' with 'g_idle_add(' pattern

23. By Alexander Sack on 2013-05-27

only update remembered screen brightniss for SCREEN_ON state
if the value from system is !=0

22. By Matt Fischer on 2013-05-24

Add a timeout setting for the activity timer.

Approved by PS Jenkins bot, Seth Forshee.

21. By Seth Forshee on 2013-05-24

powerd: Protect activity timer with a mutex

The activity timer may be reset from multiple threads. We have
a race whereby we end up with a "lost" timer event that doesn't
get cleared on input activity, thus causing the screen to turn
off while the device is in use. To fix this, serialize access to
the activity timer within reset_activity_timer() with a mutex
and make sure all code uses this function for any any activity
timer updates.

Approved by PS Jenkins bot.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.