View Single Post
Old 05-07-2023, 05:36 PM   #5
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
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
Sidebar: switching to powersave before entering suspend is meaningless, the CPUFreq governor is irrelevant in standby/suspend.

(In fact, for interactive use-cases, there's a strong case to be made for actually switching to *performance* before suspend, as on some SoCs, this will allow the device to actually enter suspend faster, as well as resume faster, too. That does imply setting it back to a more reasonable governor post-resume, though ).

----

As for the actual issue, if you're actually seeing stale *new* reads, I could somewhat understand PM screwing with it for a while, but it *should* eventually automatically jog itself back into shape :?

EDIT: i.e., I'd try polling after a much larger delay on wakeup (and/or a couple of tries).

Last edited by NiLuJe; 05-07-2023 at 05:41 PM.
NiLuJe is offline   Reply With Quote