Mika Westerberg 9f9666e653 thunderbolt: Mask ring interrupt on Intel hardware as well ... When resuming from system sleep states the driver issues following warning on Intel hardware: thunderbolt 0000:07:00.0: interrupt for TX ring 0 is already enabled The reason for this is that the commit in question did not mask the ring interrupt on Intel hardware leaving the interrupt active. Fix this by masking it also in Intel hardware. Reported-by: beld zhang <beldzhang@gmail.com> Tested-by: beld zhang <beldzhang@gmail.com> Closes: https://lore.kernel.org/linux-usb/ZHKW5NeabmfhgLbY@debian.me/ Fixes: c4af8e3fec ("thunderbolt: Clear registers properly when auto clear isn't in use") Cc: stable@vger.kernel.org Reviewed-by: Mario Limonciello <mario.limonciello@amd.com> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>		2023-05-31 10:37:21 +03:00
..
acpi.c
cap.c
ctl.c
ctl.h
debugfs.c
dma_port.c
dma_port.h
dma_test.c
domain.c
eeprom.c
icm.c
Kconfig
lc.c
Makefile
nhi.c	thunderbolt: Mask ring interrupt on Intel hardware as well	2023-05-31 10:37:21 +03:00
nhi.h
nhi_ops.c
nhi_regs.h
nvm.c
path.c
property.c
quirks.c
retimer.c
sb_regs.h
switch.c
tb.c	thunderbolt: Do not touch CL state configuration during discovery	2023-05-29 12:49:16 +03:00
tb.h
tb_msgs.h
tb_regs.h
test.c
tmu.c
tunnel.c	thunderbolt: Increase DisplayPort Connection Manager handshake timeout	2023-05-29 12:49:00 +03:00
tunnel.h
usb4.c
usb4_port.c
xdomain.c