summaryrefslogtreecommitdiffstats
path: root/virt
diff options
context:
space:
mode:
authorMa Hanghong <hanghong.ma@amd.com>2022-10-20 11:46:56 -0400
committerAlex Deucher <alexander.deucher@amd.com>2022-10-27 14:45:14 -0400
commitb1a98cf89a695d36c414653634ea7ba91b6e701f (patch)
tree7f3aa1a0c6c2bf8b232b862fe43bf2731b0f73ff /virt
parent1e8fd864afdc7a52df375e888a03b8472fc24f5d (diff)
downloadlinux-b1a98cf89a695d36c414653634ea7ba91b6e701f.tar.bz2
drm/amd/display: Wrong colorimetry workaround
[Why] For FreeSync HDR, native color space flag in AMD VSIF(BT.709) should be used when intepreting content and color space flag in VSC or AVI infoFrame should be ignored. However, it turned out some userspace application still use color flag in VSC or AVI infoFrame which is incorrect. [How] Transfer function is used when building the VSC and AVI infoFrame. Set colorimetry to BT.709 when all the following match: 1. Pixel format is YCbCr; 2. In FreeSync 2 HDR, color is COLOR_SPACE_2020_YCBCR; 3. Transfer function is TRANSFER_FUNC_GAMMA_22; Tested-by: Mark Broadworth <mark.broadworth@amd.com> Reviewed-by: Krunoslav Kovac <Krunoslav.Kovac@amd.com> Acked-by: Rodrigo Siqueira <Rodrigo.Siqueira@amd.com> Signed-off-by: Ma Hanghong <hanghong.ma@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions