9 Nov
2015
9 Nov
'15
3:09 p.m.
On Mon, Nov 09, 2015 at 03:13:09AM +0000, Oder Chiou wrote:
What makes you claim that this is "essential in case of the operation of kcontrol continuously"?
Like the Chrome OS, while the user pull the volume bar up or down, the kcontrol will be manipulated by the UI continuously and seamlessly. In this kind of case, if the "cancel_delayed_work_sync" is removed, the queue_delayed_work will be failed within 200ms after the previous queue_delayed_work, and it will not be able to make sure the power of the RC clock enabled at least 200ms, thanks.
No, it won't. To repeat what I said if you just schedule the delayed work again without cancelling then the right thing will happen.