support independent clock and LED GPIOs for Intel IPU6 platforms
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
High
|
You-Sheng Yang | ||
Jammy |
Won't Fix
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
High
|
You-Sheng Yang | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
You-Sheng Yang | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-6.0 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
High
|
You-Sheng Yang | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[SRU Justification]
[Impact]
When migrated from power_ctrl_logic driver to int3472, two additional
independent CLK/LED GPIOs other than powerdown/reset must be probed
exceptionally.
[Fix]
Vendor provided patch in
https:/
[Test Case]
Tested on both TGL/ADL platforms against nominated kernels.
[Where problems could occur]
This adds exceptional cases with fallbacks to the original function. No
one else is affected.
[Other Info]
This is an essential part for switching from power_ctrl_logic based GPIO
control mechanism to the generic, upstreamed int3472 driver. Affects all
IPU6 platforms that are to run new IPU6 driver dump in 202208.
========== original bug report ==========
Per https:/
CVE References
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux-oem-6.0 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux (Ubuntu Kinetic): | |
status: | Incomplete → In Progress |
Changed in linux-oem-6.0 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | In Progress → Fix Committed |
Changed in hwe-next: | |
status: | New → Fix Committed |
tags: | added: fixed-linux-oem-6.5 |
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 1989046
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.