Public bug reported:
[Impact]
The brightness is not changed obviously during 200 to 255.
[Fix]
max_cll defines the content light luminance for individual pixel.
max_fall defines frame-average level luminance.
Use max_fall value instead of max_cll as a limit for brightness control.
[Test]
Verified on AMD Cezanne, Barcelo and Rembrandt, also on LCD panel and
OLED panel. The brightness is changed more obivously on OLED panel, and
no affect on LCD panel.
[Where problems could occur]
Low risk, It may cause the max brightness can't be set.
Due to the schedule of OEM project, SRU this patch as SAUCE in OEM
kernels only.
** Affects: hwe-next
Importance: Undecided
Status: In Progress
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: In Progress
** Affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: In Progress
** Affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: In Progress
** Affects: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided
Status: In Progress
** Tags: oem-priority originate-from-1962647 sutton
** Tags added: oem-priority originate-from-1962647 sutton
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided
Status: New
** No longer affects: linux-oem-5.14 (Ubuntu Jammy)
** No longer affects: linux (Ubuntu Focal)
** No longer affects: linux (Ubuntu Jammy)
** No longer affects: linux-oem-5.17 (Ubuntu Focal)
** Changed in: linux-oem-5.17 (Ubuntu)
Status: New => Incomplete
** Changed in: linux-oem-5.17 (Ubuntu)
Status: Incomplete => Opinion
** Changed in: linux-oem-5.17 (Ubuntu)
Status: Opinion => In Progress
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu)
Status: New => In Progress
** Changed in: hwe-next
Status: New => Fix Committed
** Changed in: hwe-next
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1978986
Title:
[SRU][OEM-5.14/OEM-5.17][PATCH 0/1] Fix oled brightness set above
frame-average luminance on AMD
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
In Progress
Status in linux-oem-5.17 package in Ubuntu:
In Progress
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux-oem-5.17 source package in Jammy:
In Progress
Bug description:
[Impact]
The brightness is not changed obviously during 200 to 255.
[Fix]
max_cll defines the content light luminance for individual pixel.
max_fall defines frame-average level luminance.
Use max_fall value instead of max_cll as a limit for brightness control.
[Test]
Verified on AMD Cezanne, Barcelo and Rembrandt, also on LCD panel and
OLED panel. The brightness is changed more obivously on OLED panel, and
no affect on LCD panel.
[Where problems could occur]
Low risk, It may cause the max brightness can't be set.
Due to the schedule of OEM project, SRU this patch as SAUCE in OEM
kernels only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1978986/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
