diff options
| author | Hui Wang <hui.wang@canonical.com> | 2019-03-19 09:28:43 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-03-27 14:17:55 +0900 |
| commit | 1fa1bfef5f4c526ab707101f900cc09587f1dd9a (patch) | |
| tree | e3907ff1f2a234f46b718343653f69f69fbc5eb6 /kernel/sched/wait.c | |
| parent | 2b1cf1a17a41c356981f25d31bb658df53d970dc (diff) | |
| download | blackbird-obmc-linux-1fa1bfef5f4c526ab707101f900cc09587f1dd9a.tar.gz blackbird-obmc-linux-1fa1bfef5f4c526ab707101f900cc09587f1dd9a.zip | |
ALSA: hda - Don't trigger jackpoll_work in azx_resume
commit 744c67ffeb06f2d2493f4049ba0bd19698ce0adf upstream.
The commit 3baffc4a84d7 (ALSA: hda/intel: Refactoring PM code) changed
the behaviour of azx_resume(), it triggers the jackpoll_work after
applying this commit.
This change introduced a new issue, all codecs are runtime active
after S3, and will not call runtime_suspend() automatically.
The root cause is the jackpoll_work calls snd_hda_power_up/down_pm,
and it calls up_pm before snd_hdac_enter_pm is called, while calls
the down_pm in the middle of enter_pm and leave_pm is called. This
makes the dev->power.usage_count unbalanced after S3.
To fix it, let azx_resume() don't trigger jackpoll_work as before
it did.
Fixes: 3baffc4a84d7 ("ALSA: hda/intel: Refactoring PM code")
Signed-off-by: Hui Wang <hui.wang@canonical.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/sched/wait.c')
0 files changed, 0 insertions, 0 deletions
