aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/trace-event-scripting.c
diff options
context:
space:
mode:
authorTakashi Iwai <[email protected]>2019-10-28 09:10:56 +0100
committerTakashi Iwai <[email protected]>2019-10-28 11:47:59 +0100
commit1a7f60b9df614bb36d14dc0c0bc898a31b2b506f (patch)
treedbf8536d22d8ede5eeccf2c0b800c72e5d0bd30a /tools/perf/util/trace-event-scripting.c
parentf2bbdbcb075f3977a53da3bdcb7cd460bc8ae5f2 (diff)
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 <[email protected]> Cc: Chris Wilson <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Takashi Iwai <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions