Commit 31614bb8 authored by Takashi Iwai's avatar Takashi Iwai

ALSA: hda - Fix inconsistent pin states after resume

The commit [26a6cb6c: ALSA: hda - Implement a poll loop for jacks as a
module parameter] introduced the polling jack detection code, but it
also moved the call of snd_hda_jack_set_dirty_all() in the resume path
after resume/init ops call.  This caused a regression when the jack
state has been changed during power-down (e.g. in the power save
mode).  Since the driver doesn't probe the new jack state but keeps
using the cached value due to no dirty flag, the pin state remains
also as if the jack is still plugged.

The fix is simply moving snd_hda_jack_set_dirty_all() to the original
position.
Reported-by: default avatarManolo Díaz <diaz.manolo@gmail.com>
Signed-off-by: default avatarTakashi Iwai <tiwai@suse.de>
parent 42c364ac
...@@ -3654,6 +3654,7 @@ static void hda_call_codec_resume(struct hda_codec *codec) ...@@ -3654,6 +3654,7 @@ static void hda_call_codec_resume(struct hda_codec *codec)
hda_set_power_state(codec, AC_PWRST_D0); hda_set_power_state(codec, AC_PWRST_D0);
restore_shutup_pins(codec); restore_shutup_pins(codec);
hda_exec_init_verbs(codec); hda_exec_init_verbs(codec);
snd_hda_jack_set_dirty_all(codec);
if (codec->patch_ops.resume) if (codec->patch_ops.resume)
codec->patch_ops.resume(codec); codec->patch_ops.resume(codec);
else { else {
...@@ -3665,10 +3666,8 @@ static void hda_call_codec_resume(struct hda_codec *codec) ...@@ -3665,10 +3666,8 @@ static void hda_call_codec_resume(struct hda_codec *codec)
if (codec->jackpoll_interval) if (codec->jackpoll_interval)
hda_jackpoll_work(&codec->jackpoll_work.work); hda_jackpoll_work(&codec->jackpoll_work.work);
else { else
snd_hda_jack_set_dirty_all(codec);
snd_hda_jack_report_sync(codec); snd_hda_jack_report_sync(codec);
}
codec->in_pm = 0; codec->in_pm = 0;
snd_hda_power_down(codec); /* flag down before returning */ snd_hda_power_down(codec); /* flag down before returning */
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment