Fix the video can't output through WD19TB connected on TGL's Type-C port during cold-boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
koba | ||
Focal |
Invalid
|
Undecided
|
koba | ||
Groovy |
Fix Released
|
Undecided
|
koba | ||
Hirsute |
Fix Released
|
Undecided
|
koba | ||
linux-oem-5.10 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
koba | ||
Groovy |
Invalid
|
Undecided
|
Unassigned | ||
Hirsute |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[Impact]
WD19TB would report the number of lane(2-lane) and it works well on Type-C port of TGL platform.
Change the LTTPR mode to non-transparent mode, WD19TB would report the larger number of lane(4-lane). It's over the type-c port's bandwidth.
[Fix]
The patch is provided by Imre(https:/
Calculate the PBN divider value based on the rate and lane count link parameters that the driver uses for all other computation.
[Test Case]
1. Connected the WD19TB with the TGL platform's Type-C port and
connected the external monitor on WD19TB with HDMI/Displayport.
2. Cold boot the TGL platform.
3. Check the monitor can be blinked and the video can output to the monitor.
[Where problems could occur]
It's more reasonable to calculate the PBN divider based on the source's rate and lane count, not the mst's capability.
CVE References
Changed in linux (Ubuntu Hirsute): | |
assignee: | nobody → koba (kobako) |
status: | New → In Progress |
Changed in linux-oem-5.10 (Ubuntu Focal): | |
status: | New → In Progress |
assignee: | nobody → koba (kobako) |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Groovy): | |
assignee: | nobody → koba (kobako) |
status: | New → In Progress |
Changed in linux (Ubuntu Focal): | |
assignee: | nobody → koba (kobako) |
status: | New → In Progress |
tags: | added: oem-priority originate-from-1912449 somerville |
Changed in linux-oem-5.10 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
tags: | added: originate-from-1895639 |
tags: | added: originate-from-1891458 |
Changed in linux-oem-5.10 (Ubuntu Hirsute): | |
status: | New → Invalid |
Changed in linux-oem-5.10 (Ubuntu Groovy): | |
status: | New → Invalid |
Changed in linux (Ubuntu Hirsute): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Groovy): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-groovy removed: verification-needed-groovy |
Changed in linux (Ubuntu): | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu Hirsute): | |
status: | Fix Committed → Fix Released |
Changed in hwe-next: | |
status: | New → Fix Released |
Changed in linux (Ubuntu Focal): | |
status: | In Progress → Invalid |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- focal' to 'verification- done-focal' . If the problem still exists, change the tag 'verification- needed- focal' to 'verification- failed- focal'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!