Skip to content

Drive Always-on-display wakeup events using a timerfd - #296

Open
FlorentRevest wants to merge 2 commits into
masterfrom
aod-timerfd
Open

Drive Always-on-display wakeup events using a timerfd#296
FlorentRevest wants to merge 2 commits into
masterfrom
aod-timerfd

Conversation

@FlorentRevest

Copy link
Copy Markdown
Member

No description provided.

asteroid-launcher now schedules always-on-display minute tick itself
with a CLOCK_REALTIME_ALARM timerfd, so timed no longer needs to emit
the com.nokia.time wakeup_event signal that mce relayed back to it.
Remove the patch that added that event path.
The ambient (AOD) minute tick is now driven directly from the compositor
via a CLOCK_REALTIME_ALARM timerfd, and the timed "wakeup_event" patch
has been dropped from timed. Nothing emits com.nokia.time/wakeup_event
anymore, so mce's relay for it - mdy_dbus_timed_wakeup_sig() and its
handler-table registration, both added by the ambient patch - is dead
code that never fires.

Remove those two additions (and the now-unreferenced forward
declaration) from 0004-Ambient-mode-Adapt-low-power-mode. The rest of
the ambient machinery is untouched: the set_lpm_supported /
setAmbientEnabled handshake still drives the compositor's ambient mode
from the use_low_power_mode setting, and the LPM brightness handling
remains for the fbdev-based watches.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant