MobileRead Forums - View Single Post

NiLuJe · 07-18-2019, 02:15 PM

The mxcfb refresh ioctl is likely the cause of the wakeup, I can't see anything else having any potential effect (EDIT: And I don't see anything unexpected in a strace run, either). Unless disk I/O counts, somehow, but that only happens with TTF/OT fonts (EDIT: Not really, device ID requires disk I/O, too).

At least, I can see that waking the kernel. Not quite sure how that could ever translate to a touch event, though :?.

EDIT: You can test that theory by enabling --norefresh.

If you start decoding the input events, having a specific idea of exactly *which* kind of event that is might be helpful

.

/sys/power/state-extended *should* return 1 right before a suspend, but I don't rightly remember how Nickel times all of this, so this might not actually be usable.

07-18-2019, 02:15 PM	#200
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	The mxcfb refresh ioctl is likely the cause of the wakeup, I can't see anything else having any potential effect (EDIT: And I don't see anything unexpected in a strace run, either). Unless disk I/O counts, somehow, but that only happens with TTF/OT fonts (EDIT: Not really, device ID requires disk I/O, too). At least, I can see that waking the kernel. Not quite sure how that could ever translate to a touch event, though :?. EDIT: You can test that theory by enabling --norefresh. If you start decoding the input events, having a specific idea of exactly which kind of event that is might be helpful . /sys/power/state-extended should return 1 right before a suspend, but I don't rightly remember how Nickel times all of this, so this might not actually be usable. Last edited by NiLuJe; 07-18-2019 at 02:22 PM.