xavi/android_kernel_m2note/drivers/base/power, branch mm-6.0Unnamed repository; edit this file 'description' to name the repository.
https://gitea.privatedns.org/xavi/android_kernel_m2note/atom?h=mm-6.02016-11-07T12:46:48+00:00power: wakeup: partially revert some wakelock toggles2016-11-07T12:46:48+00:00cmcesar.maximo@gmail.com2016-09-19T16:03:19+00:00urn:sha1:7e89f7a6a5ea225e37c72eafbc621efe5157ad2d
This reverts msm_hsic_ws, since it's not used on MediaTek platform
Makes no issue in having this here.. But let's keep this clean...
power: wakeup: add wakelock toggles2016-09-28T13:16:04+00:00engstkeng.stk@sapo.pt2015-06-28T16:28:50+00:00urn:sha1:62738f5fc946ce0ad6cbb19361fe4586e8f55511
Signed-off-by: engstk <eng.stk@sapo.pt>
PM: Enable asynchronous noirq resume threads to save the resuming time2016-09-13T11:23:03+00:00anarkia1976stefano.villa1976@gmail.com2015-06-02T18:11:44+00:00urn:sha1:7a15530b17dad225d67aab23c8230e5a2981b45b
Subject [PATCH] PM: Enable asynchronous noirq resume threads to save the resuming time
From Chuansheng Liu <>
Date Tue, 14 Jan 2014 15:18:08 +0800
Currently, the dpm_resume_noirq() is done synchronously, and for PCI devices
pci_pm_resume_noirq():
pci_pm_resume_noirq()
pci_pm_default_resume_early()
pci_power_up()
pci_raw_set_power_state()
Which set the device from D3hot to D0 mostly, for every device, there will
be one 10ms(pci_pm_d3_delay) to wait.
Hence normally dpm_resume_noirq() will cost > 100ms, which is bigger for mobile
platform.
Here implementing it with asynchronous way which will reduce much.
For example below, The 80% time is saved.
With synchronous way:
[ 1411.272218] PM: noirq resume of devices complete after 92.223 msecs
With asynchronous way:
[ 110.616735] PM: noirq resume of devices complete after 10.544 msecs
Signed-off-by: Liu, Chuansheng <chuansheng.liu@intel.com>
first commit2016-08-15T02:19:42+00:00Meizu OpenSourcepatchwork@meizu.com2016-08-15T02:19:42+00:00urn:sha1:d2e1446d81725c351dc73a03b397ce043fb18452