aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/omapdrm/omap_plane.c
diff options
context:
space:
mode:
authorDave Stevenson <[email protected]>2022-02-21 09:59:14 +0000
committerMaxime Ripard <[email protected]>2022-02-25 16:57:14 +0000
commit9a48ab11714c955456fefdd4ab532d324fbef563 (patch)
treeb8618938b324ff3df3ec6662e72198fce310bf34 /drivers/gpu/drm/omapdrm/omap_plane.c
parentdrm/sun4i: layer: Remove redundant zpos initialisation (diff)
downloadkernel-9a48ab11714c955456fefdd4ab532d324fbef563.tar.gz
kernel-9a48ab11714c955456fefdd4ab532d324fbef563.zip
drm/object: Add default color encoding and range value at reset
The drm_plane_create_color_properties() function asks for an initial value for the color encoding and range, and will set the associated plane state variable with that value if a state is present. However, that function is usually called at a time where there's no state yet. Since the drm_plane_state reset helper doesn't take care of reading that value when it's called, it means that in most cases the initial value will be 0 (so DRM_COLOR_YCBCR_BT601 and DRM_COLOR_YCBCR_LIMITED_RANGE, respectively), or the drivers will have to work around it. Let's add some code in __drm_atomic_helper_plane_state_reset() to get the initial encoding and range value if the property has been attached in order to fix this. Reviewed-by: Harry Wentland <[email protected]> Signed-off-by: Dave Stevenson <[email protected]> Signed-off-by: Maxime Ripard <[email protected]> Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'drivers/gpu/drm/omapdrm/omap_plane.c')
0 files changed, 0 insertions, 0 deletions