From: "Heiko Stübner" <heiko@sntech.de>
To: "Igor Paunovic" <royalnet026@gmail.com>,
"Jan Claußen" <jan.claussen10@web.de>
Cc: Igor Paunovic <royalnet026@gmail.com>,
Sandy Huang <hjc@rock-chips.com>,
Maxime Ripard <mripard@kernel.org>,
Diederik de Haas <diederik@cknow-tech.com>,
linux-rockchip@lists.infradead.org,
dri-devel@lists.freedesktop.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH v2] drm/rockchip: dw_hdmi_qp: attach the HDMI Colorspace connector property
Date: Tue, 20 Oct 2026 16:01:11 +0200 [thread overview]
Message-ID: <2318151.NgBsaNRSFp@diego> (raw)
In-Reply-To: <2070944.yKVeVyVuyW@diego>
Am Dienstag, 20. Oktober 2026, 15:59:18 Mitteleuropäische Sommerzeit schrieb Heiko Stübner:
> Hey Igor,
>
> Am Mittwoch, 9. September 2026, 13:25:40 Mitteleuropäische Sommerzeit schrieb Igor Paunovic:
> > Gentle ping on this one - it has been a month without review.
> >
> > I re-checked it today rather than assuming: it still applies cleanly on
> > drm-misc-next (8ce26b09f652), with no offset and no fuzz, and nothing
> > merged since attaches the Colorspace property for this connector. So the
> > gap is still there: without it KWin reports the outputs as "HDR:
> > incapable" on RK3588 even though the sinks and the rest of the kernel
> > side are ready.
> >
> > The patch is independent of Cristian's dw-hdmi-qp HDMI 2.0 series; that
> > series is not in drm-misc-next yet, and when it lands its patch 34 will
> > touch the first context line of my hunk, so I will rebase and resend as
> > v3 at that point. The change itself does not overlap with it.
> >
> > Happy to respin if you would rather have it on top of that series.
>
> yes, the hdmi2.0 series landed meanwhile.
>
> But there is also
> https://lore.kernel.org/dri-devel/20261018143135.5745-3-jan.claussen10@web.de/
>
> which does way more to that colorspace thing, especially doing something
> into the direction of HDR support it seems.
>
> So really no clue how that all is supposed to work ;-)
and of course there is also your HDR'ish-series in
https://lore.kernel.org/dri-devel/20260808095749.9428-1-royalnet026@gmail.com/
way confusing.
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2026-10-20 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 15:33 [PATCH v2] drm/rockchip: dw_hdmi_qp: attach the HDMI Colorspace connector property Igor Paunovic
2026-08-05 16:11 ` Diederik de Haas
2026-09-09 11:25 ` Igor Paunovic
2026-10-20 13:59 ` Heiko Stübner
2026-10-20 14:01 ` Heiko Stübner [this message]
[not found] <20260805154418.8133B1F00A3A@smtp.kernel.org>
2026-08-05 15:51 ` Igor Paunovic
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=2318151.NgBsaNRSFp@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=diederik@cknow-tech.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.com \
--cc=jan.claussen10@web.de \
--cc=linux-rockchip@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=royalnet026@gmail.com \
/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