* AMD Yellow Carp provides integrated USB4 host controllers
* When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring"
[Test Plan]
* Plug in USB4 device or TBT3 to AMD Yellow Carp host
* Ensure that PCI topology has populated
* Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0"
* Try to run `boltctl enroll $UUID`
[Where problems could occur]
* Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt.
* This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time.
[Other Info]
* This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy.
* It is fixed in bolt 0.9.1 or later release.
* To solve the SRU, will backport 0.9.2 release from Jammy.
[Impact]
* AMD Yellow Carp provides integrated USB4 host controllers
* When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring"
[Test Plan]
* Plug in USB4 device or TBT3 to AMD Yellow Carp host thunderbolt/ devices/ DEVICE/ authorized is "0"
* Ensure that PCI topology has populated
* Observe that /sys/bus/
* Try to run `boltctl enroll $UUID`
[Where problems could occur]
* Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt.
* This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time.
[Other Info]
* This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy.
* It is fixed in bolt 0.9.1 or later release.
* To solve the SRU, will backport 0.9.2 release from Jammy.