Quote:
Originally Posted by jscris
So I'm probably wrong. 
Attached. |
Both yes and no.
Also, this may be firmware version specific.
Post (or re-post) your firmware version and if it is still the factory or the customer flavor.
There are two things at work here - -
You have the device running on the secondary battery (the one in the cover, the cover is plugged into the Kindle).
Other Kindle models do not have a secondary battery.
Oops. This is a KV not a KOA.
The suspend code IRQ handling in the adapter module is not correct for your model Kindle, and perhaps not correct for others:
Code:
161017:170527 [132000.846573] PM: suspend of devices complete after 90.659 msecs
161017:170527 [132000.846984] PM: late suspend of devices complete after 0.393 msecs
161017:170527 [132000.847312] triggered: wake_irq_isr[0-3]: 0x0, 0x0, 0x200, 0x0
161017:170527 [132000.847323] gpio4 triggered 0x100000 (0xfed58f71/0x104080)
161017:170527 [132000.847989] PM: early resume of devices complete after 0.216 msecs
Note:
left column: YYMMDD:User land time
next column, bracketed: Kernel time with microsecond resolution.
132000.847312 - 132000.846984 is not much of a 'sleep', in fact, it isn't even a short nap on a computer's timescale.
About the only way that can happen, is that:
Code:
161017:170527 [132000.847312] triggered: wake_irq_isr[0-3]: 0x0, 0x0, 0x200, 0x0
161017:170527 [132000.847323] gpio4 triggered 0x100000 (0xfed58f71/0x104080)
was a pre-existing condition (not properly masked when going to sleep).
= = = = =
Yes, I can read the log but I can't do anything about the code.
That will have to be up to the author of this add-in.