Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content
Commit c6aced20 authored by Alec Mouri's avatar Alec Mouri
Browse files

Remove extra layering of HDR capabilities on top of HWC

SurfaceFlinger claimed to always handle HDR10 and HLG content. This was
because initial handling of HDR content was done by hacking in Y410
support and applying a special GPU shader. However, the Y410 path has
not been used since at least Android 12 when SkiaRenderEngine stopped
supporting it.

The resulting side effect is that some WCG-capable devices are reporting
themselves as HDR-capable to apps. This is not desirable by OEMs who may
install a low dynamic range panel. And, on such panels, an SDR rendition
would likely both look better and have cheaper power consumption.

This change allows for OEMs to report that they don't support HDR. Note
that this patch does not change color management: OEMs will still be
required to accept HLG or HDR10 content and color manage correctly if
the display receives this content. I.e., the HdrCapabilities API will
tell the app that they *should not* submit HDR content, not that they
*cannot*.

Bug: 281623165
Test: libcompositionengine_test
Change-Id: I7c7dc150fd92e580330e31f9ebfe29e645510cdf
parent 994761f2
Loading
Loading
Loading
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment