summaryrefslogtreecommitdiff
path: root/security/lockdown
diff options
context:
space:
mode:
authorTakashi Iwai <tiwai@suse.de>2019-10-28 11:10:56 +0300
committerTakashi Iwai <tiwai@suse.de>2019-10-28 13:47:59 +0300
commit1a7f60b9df614bb36d14dc0c0bc898a31b2b506f (patch)
treedbf8536d22d8ede5eeccf2c0b800c72e5d0bd30a /security/lockdown
parentf2bbdbcb075f3977a53da3bdcb7cd460bc8ae5f2 (diff)
downloadlinux-1a7f60b9df614bb36d14dc0c0bc898a31b2b506f.tar.xz
Revert "ALSA: hda: Flush interrupts on disabling"
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>
Diffstat (limited to 'security/lockdown')
0 files changed, 0 insertions, 0 deletions