summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorMika Westerberg <mika.westerberg@linux.intel.com>2019-11-11 13:25:44 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-12-05 09:21:27 +0100
commitc01cffbcdb5273c64a2b4003220a27042afc87c2 (patch)
tree077d34f1ee8ab026138aa761bb85e494a082097a /net
parent728fd8373780ed9ce1a9af9904c13c5578a55c7f (diff)
downloadlinux-stable-c01cffbcdb5273c64a2b4003220a27042afc87c2.tar.gz
linux-stable-c01cffbcdb5273c64a2b4003220a27042afc87c2.tar.bz2
linux-stable-c01cffbcdb5273c64a2b4003220a27042afc87c2.zip
thunderbolt: Power cycle the router if NVM authentication fails
commit 7a7ebfa85f4fac349f3ab219538c44efe18b0cf6 upstream. On zang's Dell XPS 13 9370 after Thunderbolt NVM firmware upgrade the Thunderbolt controller did not come back as expected. Only after the system was rebooted it became available again. It is not entirely clear what happened but I suspect the new NVM firmware image authentication failed for some reason. Regardless of this the router needs to be power cycled if NVM authentication fails in order to get it fully functional again. This modifies the driver to issue a power cycle in case the NVM authentication fails immediately when dma_port_flash_update_auth() returns. We also need to call tb_switch_set_uuid() earlier to be able to fetch possible NVM authentication failure when DMA port is added. Link: https://bugzilla.kernel.org/show_bug.cgi?id=205457 Reported-by: zang <dump@tzib.net> Cc: stable <stable@vger.kernel.org> Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions