{"push_id":822900543,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"d2607d964367a8c30e0f63168f69d2a9d9c3eb2b","before":"19984a53985dee2a3ea5cbddee05149a1323fe73","commits":[{"sha":"d2607d964367a8c30e0f63168f69d2a9d9c3eb2b","author":{"email":"ca2e34e1958955302f317311f66bb8462b7e1dce@gmail.com","name":"alexax66"},"message":"PM / Sleep: Print name of wakeup source that aborts suspend\nA driver or app may repeatedly request a wakeup source while the system\nis attempting to enter suspend, which may indicate a bug or at least\npoint out a highly active system component that is responsible for\ndecreased battery life on a mobile device.  Even when the incidence\nof suspend abort is not severe, identifying wakeup sources that\nfrequently abort suspend can be a useful clue for power management\nanalysis.\n\nIn some cases the existing stats can point out the offender where there is\nan unexpectedly high activation count that stands out from the others, but\nin other cases the wakeup source frequently taken just after the rest of\nthe system thinks its time to suspend might not stand out in the overall\nstats.\n\nIt is also often useful to have information about what's been happening\nrecently, rather than totals of all activity for the system boot.\n\nIt's suggested to dump a line about which wakeup source\naborted suspend to aid analysis of these situations.\n\nSigned-off-by: Todd Poynor <toddpoynor@google.com>\nSigned-off-by: Rafael J. Wysocki <rjw@sisk.pl>\n\nOriginal commit: https://github.com/CyanogenMod/android_kernel_samsung_d2/commit/a08bc4bc4bcfaf30b3060ae64b1a3dd8276b46dc","distinct":true,"url":"https://api.github.com/repos/alexax66/CM12.1_kernel_serranodsxx/commits/d2607d964367a8c30e0f63168f69d2a9d9c3eb2b"}]}