*** spiiroin__ is now known as spiiroin | 06:11 | |
spiiroin | piggz: dsme & rtc wakeups: there are some internal to dsme activity (thermal/battery/like checks), but mostly it depends / ought to depend on iphb clients | 06:16 |
---|---|---|
T42 | <adampigg> Spiiroin: see wakeups here, every minute looks loke rtc, is that normal? https://paste.mozilla.org/2Vi9cGKO | 08:24 |
spiiroin | @adampigg afaict it is process watchdog activity, happening at multiples of hw watchdog kick period (=12 secs) -> mce confirms to dsme that it is still alive and performs some periodic activity while the system is up and doing something (= at least that hw wd kick) anyway | 09:09 |
spiiroin | there is a connection between hw wd kicking and rtc reprogramming (the next rtc wakeup can end up being reprogrammed more in to future) | 09:10 |
spiiroin | but this does not look like it was initiated due to rtc wakeups | 09:10 |
spiiroin | in case of rtc wakeup there is (for the purposes of cpu-keepalive stuff) dbus ipc between dsme and mce, protected by wakelock (acquired by dsme and released by mce) | 09:13 |
spiiroin | hmm, unless you meant starting from 21:32:03? there are cka_dbus_handle_wakeup_cb events about once/minute (=rtc wakeup) | 09:26 |
spiiroin | there seems to be some bt activity close to those, so it could be bt stack scheduling wakeups with nemo-keepalive -> which could result in rtc wakeups | 09:28 |
spiiroin | if so, it could be more or less expected "depends on iphb client behavior" thing | 09:30 |
T42 | <måttat> @Mister_Magister can you unban me from your channel please | 21:21 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!