All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Paunovic <royalnet026@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: Igor Paunovic <royalnet026@gmail.com>,
	Sandy Huang <hjc@rock-chips.com>,
	Andy Yan <andy.yan@rock-chips.com>,
	Maxime Ripard <mripard@kernel.org>,
	Cristian Ciocaltea <cristian.ciocaltea@collabora.com>,
	Diederik de Haas <diederik@cknow-tech.com>,
	dri-devel@lists.freedesktop.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2] drm/rockchip: dw_hdmi_qp: attach the HDMI Colorspace connector property
Date: Wed,  9 Sep 2026 13:25:40 +0200	[thread overview]
Message-ID: <20260909112543.6913-1-royalnet026@gmail.com> (raw)
In-Reply-To: <20260805153416.8459-1-royalnet026@gmail.com>

Hi Heiko,

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.

Thanks,
Igor

      parent reply	other threads:[~2026-09-09 11:26 UTC|newest]

Thread overview: 5+ 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 15:44 ` sashiko-bot
2026-08-05 15:51   ` Igor Paunovic
2026-08-05 16:11 ` Diederik de Haas
2026-09-09 11:25 ` Igor Paunovic [this message]

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=20260909112543.6913-1-royalnet026@gmail.com \
    --to=royalnet026@gmail.com \
    --cc=andy.yan@rock-chips.com \
    --cc=cristian.ciocaltea@collabora.com \
    --cc=diederik@cknow-tech.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=hjc@rock-chips.com \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=mripard@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.