summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorNicolas Frattaroli <nicolas.frattaroli@collabora.com>2026-06-09 14:43:53 +0200
committerDaniel Stone <daniels@collabora.com>2026-06-09 21:03:50 +0100
commitf5873533bf99ee98237141f33ba15e04170498f4 (patch)
tree87393e3c499f0e0db785a52d3a9cc5b4a07cadf2 /include
parent9743ab2c18204572400dbd8f579ccb85a14d2ad7 (diff)
downloadlinux-f5873533bf99ee98237141f33ba15e04170498f4.tar.gz
linux-f5873533bf99ee98237141f33ba15e04170498f4.zip
drm/bridge: Act on the DRM color format property
The new DRM color format property allows userspace to request a specific color format on a connector. In turn, this fills the connector state's color_format member to switch color formats. Make drm_bridges consider the color_format set in the connector state during the atomic bridge check. Call into the connector function to get the connector state's connector color format. For bridge connectors including an HDMI bridge, this will make use of whatever the HDMI implementation set as output formats, and AUTO will never be part of the rejection logic. Reject any output bus formats that do not correspond to the requested color format. DRM_CONNECTOR_COLOR_FORMAT_AUTO is always accepted as a matching color format for a bus format, meaning that non-HDMI bridge chains will end up picking the first bus format choice that works, as has already been the case previously. Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com> Reviewed-by: Daniel Stone <daniel@fooishbar.org> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com> Link: https://patch.msgid.link/20260609-color-format-v17-6-35739b5782cc@collabora.com Signed-off-by: Daniel Stone <daniels@collabora.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions