{"push_id":730266915,"size":1,"distinct_size":1,"ref":"refs/heads/lollipop","head":"6e44714bb138a5bf01d2eb44e8af216ac20e9082","before":"e2dfe083bad2a34c57d1dcdc736be1d850a28f1f","commits":[{"sha":"6e44714bb138a5bf01d2eb44e8af216ac20e9082","author":{"email":"bb05168246ed1a6b66d0e7b1ffb0c5e3707764ca@codeaurora.org","name":"Junjie Wu"},"message":"cpufreq: Disable light-weight init/teardown during suspend/resume\n\nLight-weight init/teardown is introduced to preserve file permission and\nreduce suspend/resume latency. However, it doesn't work correctly if\nmultiple CPUs controlled by same policy can all go offline.\n\nSuspend and resume removes and adds back CPUs in the same order for\nnon-boot CPUs. Say CPU2 and CPU3 are both online when suspend starts.\nCPU2 goes offline first, handing policy and sysfs over to CPU3. Then\nCPU3 goes offline. Due to light-weight teardown, CPU3 still owns the\npolicy and sysfs files.\n\nWhen CPU2 comes online after resume, it calls update_policy_cpu() to take\nback the policy ownership, but sysfs is not touched. Now CPU2 is online,\nwith an active policy, but no sysfs folder. In additions, when CPU3 comes\nonline, it will attempt to create a symlink while owning the real sysfs\nfolder.\n\nTo really fix this issue, special handling for sysfs and symlinks is\nrequired during suspend and resume. This requires non-trivial refactoring\nof certain functions.\n\nTemporarly disable light-weight init/teardown until a solution is found.\n\nChange-Id: I485483244954129fa405bc5ef1a5e0da5c05a7d5\nSigned-off-by: Junjie Wu <junjiew@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Starship-Android/android_kernel_moto_shamu/commits/6e44714bb138a5bf01d2eb44e8af216ac20e9082"}]}