diff options
author | Mika Westerberg <mika.westerberg@linux.intel.com> | 2020-11-10 11:34:07 +0300 |
---|---|---|
committer | Mika Westerberg <mika.westerberg@linux.intel.com> | 2020-11-30 14:39:24 +0300 |
commit | 661b19473bf3ac0924560f0cbf84c15458b3c8de (patch) | |
tree | 32a36bb669b6a4bc3536f3386107a2853a01ec6e /sound | |
parent | 463e48fa544826898791085508459de246fc4c09 (diff) | |
download | linux-661b19473bf3ac0924560f0cbf84c15458b3c8de.tar.gz linux-661b19473bf3ac0924560f0cbf84c15458b3c8de.tar.bz2 linux-661b19473bf3ac0924560f0cbf84c15458b3c8de.zip |
thunderbolt: Perform USB4 router NVM upgrade in two phases
The currect code expects that the router returns back the status of the
NVM authentication immediately. When tested against a real USB4 device
what happens is that the router is reset and only after that the result
is updated in the ROUTER_CS_26 register status field. This also seems to
align better what the spec suggests.
For this reason do the same what we already do with the Thunderbolt 3
devices and perform the NVM upgrade in two phases. First start the
NVM_AUTH router operation and once the router is added back after the
reset read the status in ROUTER_CS_26 and expose it to the userspace
accordingly.
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'sound')
0 files changed, 0 insertions, 0 deletions