Stop using get_scalar_status command in Dell AIO uart backlight driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Medium
|
AceLan Kao | ||
Bionic |
Fix Released
|
Medium
|
Unassigned | ||
Eoan |
Fix Released
|
Medium
|
Unassigned | ||
Focal |
Won't Fix
|
Undecided
|
AceLan Kao | ||
Groovy |
Won't Fix
|
Undecided
|
AceLan Kao | ||
Hirsute |
Fix Released
|
Medium
|
AceLan Kao | ||
linux-oem-5.10 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
AceLan Kao | ||
linux-oem-osp1 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
The get_scalar_status command was provided by ODM engineer and was newly introduced to determinate whether scalar is responsible for the backlight adjustment. That guy asked the scalar vendor to add this command and the command works as expected. But there is already a command in the Dell AIO scalar UART command spec. which can do the same thing since 2015, and the newly introduced get_scalar_status command is undocumented. To prevent from introducing regression in the future and to align with what Windows uses, replace this command with get_display_mode command.
[Fix]
Replace get_scalar_status command with get_display_mode command.
[Test]
Verified on new Dell AIO platforms.
[Regression Potential]
Low, the command is already in the spec. since 2015.
CVE References
no longer affects: | linux-oem-osp1 (Ubuntu Eoan) |
no longer affects: | linux-oem-osp1 (Ubuntu Focal) |
Changed in linux-oem-osp1 (Ubuntu Bionic): | |
status: | New → Fix Committed |
tags: | added: patch |
Changed in linux (Ubuntu Eoan): | |
status: | New → In Progress |
Changed in linux (Ubuntu Bionic): | |
status: | Incomplete → In Progress |
Changed in linux (Ubuntu Focal): | |
status: | Incomplete → In Progress |
Changed in linux-oem-osp1 (Ubuntu): | |
status: | New → Invalid |
Changed in linux (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Eoan): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Focal): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Eoan): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-osp1 (Ubuntu): | |
status: | Invalid → Fix Released |
tags: |
added: verification-done-bionic verification-done-eoan removed: verification-needed-bionic verification-needed-eoan |
no longer affects: | linux (Ubuntu Focal) |
Changed in linux (Ubuntu Focal): | |
status: | New → In Progress |
Changed in linux (Ubuntu Groovy): | |
assignee: | nobody → AceLan Kao (acelankao) |
status: | New → In Progress |
Changed in linux (Ubuntu Focal): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux (Ubuntu Hirsute): | |
assignee: | nobody → AceLan Kao (acelankao) |
no longer affects: | linux-oem-5.10 (Ubuntu Bionic) |
no longer affects: | linux-oem-5.10 (Ubuntu Groovy) |
no longer affects: | linux-oem-5.10 (Ubuntu Hirsute) |
no longer affects: | linux-oem-osp1 (Ubuntu Focal) |
no longer affects: | linux-oem-osp1 (Ubuntu Groovy) |
no longer affects: | linux-oem-osp1 (Ubuntu Hirsute) |
Changed in linux-oem-5.10 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.10 (Ubuntu Focal): | |
assignee: | nobody → AceLan Kao (acelankao) |
status: | New → In Progress |
tags: | added: oem-priority originate-from-1904520 somerville |
Changed in linux-oem-5.10 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-focal removed: verification-needed-focal |
Changed in hwe-next: | |
status: | New → Fix Released |
Changed in linux (Ubuntu Focal): | |
status: | In Progress → Won't Fix |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1865402
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.