From: "Jan Claußen" <jan.claussen10@web.de>
To: "Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Andrzej Hajda" <andrzej.hajda@intel.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Robert Foss" <rfoss@kernel.org>,
"Laurent Pinchart" <Laurent.pinchart@ideasonboard.com>,
"Jonas Karlman" <jonas@kwiboo.se>,
"Jernej Skrabec" <jernej.skrabec@gmail.com>,
"Luca Ceresoli" <luca.ceresoli@bootlin.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Daniel Stone" <daniels@collabora.com>,
"Cristian Ciocaltea" <cristian.ciocaltea@collabora.com>,
"Nicolas Frattaroli" <nicolas.frattaroli@collabora.com>,
"Jan Claußen" <jan.claussen10@web.de>
Cc: dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/7] drm: Add colorspace property support to the HDMI helpers
Date: Sun, 18 Oct 2026 16:31:06 +0200 [thread overview]
Message-ID: <20261018143135.5745-1-jan.claussen10@web.de> (raw)
HDMI connectors set up through drmm_connector_hdmi_init() don't expose
the colorspace property, so userspace can't signal BT.2020 colorimetry
for HDR. KWin, for example, doesn't offer HDR without it.
This series lets drivers declare which colorspaces they support and has
the HDMI helpers create the property and force a modeset when it
changes. dw-hdmi-qp on RK3588 is the first user.
Tested on a Radxa Rock 5B (RK3588) with an LG OLED55B87LC in KDE
Plasma 6.7.5. Only BT.2020 RGB is tested.
Changes in v4:
- Set the VOP2 color space from the connector colorspace, so YCbCr output
is converted with the matching matrix (Sashiko)
Changes in v3:
- Move colorspace handling into the HDMI helpers (Maxime)
- Let drivers declare supported colorspaces instead of exposing all
- Split into a series
Changes in v2:
- Fix possible null pointer dereferencing requested by the Sashiko bot
v3: https://lore.kernel.org/all/20261018123037.19560-1-jan.claussen10@web.de
v2: https://lore.kernel.org/all/20261011142733.7806-1-jan.claussen10@web.de
v1: https://lore.kernel.org/all/20261011132024.2833-1-jan.claussen10@web.de
Jan Claußen (7):
drm/connector: Fix typo in colorspace error messages
drm/display: hdmi-state-helper: Force modeset on colorspace change
drm/connector: hdmi: Create the colorspace property
drm/bridge-connector: Pass supported colorspaces to the HDMI helpers
drm/bridge: dw-hdmi-qp: Forward supported colorspaces from platform
data
drm/rockchip: dw_hdmi_qp: Set the VOP2 color space from the connector
drm/rockchip: dw_hdmi_qp: Advertise BT.709 and BT.2020 colorimetries
drivers/gpu/drm/bridge/synopsys/dw-hdmi-qp.c | 3 +++
.../gpu/drm/display/drm_bridge_connector.c | 4 ++++
.../gpu/drm/display/drm_hdmi_state_helper.c | 3 ++-
drivers/gpu/drm/drm_connector.c | 17 ++++++++++++----
.../gpu/drm/rockchip/dw_hdmi_qp-rockchip.c | 20 +++++++++++++++++++
include/drm/bridge/dw_hdmi_qp.h | 2 ++
include/drm/drm_bridge.h | 7 +++++++
include/drm/drm_connector.h | 7 +++++++
8 files changed, 58 insertions(+), 5 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-18 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 14:31 Jan Claußen [this message]
2026-10-18 14:31 ` [PATCH v4 6/7] drm/rockchip: dw_hdmi_qp: Set the VOP2 color space from the connector Jan Claußen
2026-10-18 14:31 ` [PATCH v4 7/7] drm/rockchip: dw_hdmi_qp: Advertise BT.709 and BT.2020 colorimetries Jan Claußen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261018143135.5745-1-jan.claussen10@web.de \
--to=jan.claussen10@web.de \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=daniels@collabora.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox