Skip to content

Conversation

@setotau
Copy link

@setotau setotau commented Nov 3, 2025

Both panels for xiaomi-clover and xiaomi-clover-plus support content-adaptive brightness control, so add needed programming sequences to enable this feature and configure backlight IC's for both devices to support this.

@minlexx
Copy link
Member

minlexx commented Nov 3, 2025

seems like cabc_on / cabc_off could be separate functions, cacbc_on being shared between 2 panels

@setotau
Copy link
Author

setotau commented Nov 3, 2025

Other panel drivers contain CABC-related logic both in init and off functions

@setotau setotau force-pushed the setotau/qcom-sdm660-6.18.y-clover-brightness-rework branch 2 times, most recently from d07dca1 to 05156fc Compare November 3, 2025 17:21
NT51021-based panels support content-adaptive brightness control by
generating a PWM signal for backlight driver IC. Content adaptation
means that content grey level scale can be increased while
simultaneously decreasing brightness of the backlight to achieve
same perceived brightness. This makes the power consumption of
backlight be reduced with keeping acceptable display quality.

Signed-off-by: Nickolay Goppen <setotau@mainlining.org>
The qcom-wled backlight controller supports CABC, so add a property,
that enables this feature to qcom-wled node to follow-up added CABC
support to the panel driver.

Signed-off-by: Nickolay Goppen <setotau@mainlining.org>
The LP8556 backlight controller also supports the CABC feature, so
configure it to support this. Also remove a comment about EPROM start,
and clarify some EPROM values' meaning.

Signed-off-by: Nickolay Goppen <setotau@mainlining.org>
@setotau setotau force-pushed the setotau/qcom-sdm660-6.18.y-clover-brightness-rework branch from 05156fc to 128bc94 Compare November 3, 2025 17:29
Copy link
Member

@minlexx minlexx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming you've tested that panel on clover/plus still works...

@setotau
Copy link
Author

setotau commented Nov 3, 2025

Yes, it works fine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants