diff options
| author | Takashi Iwai <tiwai@suse.de> | 2019-10-28 09:10:56 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2019-11-06 12:43:41 +0100 |
| commit | 79fd25943d0fcedd032c0a337c8ff3e01eda999d (patch) | |
| tree | c46a8ac0b1f9baaa7da32e52fe1db4fa293c653e /lib/debug_info.c | |
| parent | 1ff779c530064839511d5b327cd2ade7a17a2651 (diff) | |
| download | linux-stable-79fd25943d0fcedd032c0a337c8ff3e01eda999d.tar.gz linux-stable-79fd25943d0fcedd032c0a337c8ff3e01eda999d.tar.bz2 linux-stable-79fd25943d0fcedd032c0a337c8ff3e01eda999d.zip | |
Revert "ALSA: hda: Flush interrupts on disabling"
[ Upstream commit 1a7f60b9df614bb36d14dc0c0bc898a31b2b506f ]
This reverts commit caa8422d01e983782548648e125fd617cadcec3f.
It turned out that this commit caused a regression at shutdown /
reboot, as the synchronize_irq() calls seems blocking the whole
shutdown. Also another part of the change about shuffling the call
order looks suspicious; the azx_stop_chip() call disables the CORB /
RIRB while the others may still need the CORB/RIRB update.
Since the original commit itself was a cargo-fix, let's revert the
whole patch.
Fixes: caa8422d01e9 ("ALSA: hda: Flush interrupts on disabling")
BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=205333
BugLinK: https://bugs.freedesktop.org/show_bug.cgi?id=111174
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Link: https://lore.kernel.org/r/20191028081056.22010-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'lib/debug_info.c')
0 files changed, 0 insertions, 0 deletions