From: Neil Armstrong <narmstrong@baylibre.com>
To: Jonas Karlman <jonas@kwiboo.se>,
"a.hajda@samsung.com" <a.hajda@samsung.com>,
"Laurent.pinchart@ideasonboard.com"
<Laurent.pinchart@ideasonboard.com>
Cc: "jernej.skrabec@siol.net" <jernej.skrabec@siol.net>,
"khilman@baylibre.com" <khilman@baylibre.com>,
"zhengyang@rock-chips.com" <zhengyang@rock-chips.com>,
"maxime.ripard@bootlin.com" <maxime.ripard@bootlin.com>,
"wens@csie.org" <wens@csie.org>,
"hjc@rock-chips.com" <hjc@rock-chips.com>,
"heiko@sntech.de" <heiko@sntech.de>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] drm/bridge: dw-hdmi: Add support for HDR metadata
Date: Thu, 20 Jun 2019 16:40:12 +0200 [thread overview]
Message-ID: <085dc3be-20e5-b2fe-4c02-bf4a4d1473da@baylibre.com> (raw)
In-Reply-To: <VI1PR03MB420621617DDEAB3596700DE0AC1C0@VI1PR03MB4206.eurprd03.prod.outlook.com>
Hi Andrzej,
Gentle ping, could you review the dw-hdmi changes here ?
Thanks,
Neil
On 26/05/2019 23:18, Jonas Karlman wrote:
> Add support for HDR metadata using the hdr_output_metadata connector property,
> configure Dynamic Range and Mastering InfoFrame accordingly.
>
> A drm_infoframe flag is added to dw_hdmi_plat_data that platform drivers
> can use to signal when Dynamic Range and Mastering infoframes is supported.
> This flag is needed because Amlogic GXBB and GXL report same DW-HDMI version,
> and only GXL support DRM InfoFrame.
>
> The first patch add functionality to configure DRM InfoFrame based on the
> hdr_output_metadata connector property.
>
> The remaining patches sets the drm_infoframe flag on some SoCs supporting
> Dynamic Range and Mastering InfoFrame.
>
> Note that this was based on top of drm-misc-next and Neil Armstrong's
> "drm/meson: Add support for HDMI2.0 YUV420 4k60" series at [1]
>
> [1] https://patchwork.freedesktop.org/series/58725/#rev2
>
> Jonas Karlman (4):
> drm/bridge: dw-hdmi: Add Dynamic Range and Mastering InfoFrame support
> drm/rockchip: Enable DRM InfoFrame support on RK3328 and RK3399
> drm/meson: Enable DRM InfoFrame support on GXL, GXM and G12A
> drm/sun4i: Enable DRM InfoFrame support on H6
>
> drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 109 ++++++++++++++++++++
> drivers/gpu/drm/bridge/synopsys/dw-hdmi.h | 37 +++++++
> drivers/gpu/drm/meson/meson_dw_hdmi.c | 5 +
> drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 2 +
> drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c | 2 +
> drivers/gpu/drm/sun4i/sun8i_dw_hdmi.h | 1 +
> include/drm/bridge/dw_hdmi.h | 1 +
> 7 files changed, 157 insertions(+)
>
next prev parent reply other threads:[~2019-06-20 14:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 21:18 [PATCH 0/4] drm/bridge: dw-hdmi: Add support for HDR metadata Jonas Karlman
2019-05-26 21:19 ` [PATCH 1/4] drm/bridge: dw-hdmi: Add Dynamic Range and Mastering InfoFrame support Jonas Karlman
2019-06-05 12:57 ` Neil Armstrong
2019-06-24 13:40 ` Andrzej Hajda
2019-05-26 21:20 ` [PATCH 2/4] drm/rockchip: Enable DRM InfoFrame support on RK3328 and RK3399 Jonas Karlman
2019-06-14 9:29 ` Heiko Stuebner
2019-06-24 14:43 ` Andrzej Hajda
2019-05-26 21:20 ` [PATCH 3/4] drm/meson: Enable DRM InfoFrame support on GXL, GXM and G12A Jonas Karlman
2019-06-05 12:55 ` Neil Armstrong
2019-06-24 14:59 ` Andrzej Hajda
2019-06-26 9:16 ` Neil Armstrong
2019-05-26 21:20 ` [PATCH 4/4] drm/sun4i: Enable DRM InfoFrame support on H6 Jonas Karlman
2019-06-24 15:03 ` Andrzej Hajda
2019-06-24 15:05 ` Jernej Škrabec
2019-06-24 15:49 ` Andrzej Hajda
2019-06-24 15:56 ` Chen-Yu Tsai
2019-06-24 16:03 ` Jernej Škrabec
2019-06-24 16:07 ` Chen-Yu Tsai
2019-06-24 16:59 ` Andrzej Hajda
2019-05-28 17:03 ` [PATCH 0/4] drm/bridge: dw-hdmi: Add support for HDR metadata Jernej Škrabec
2019-06-20 14:40 ` Neil Armstrong [this message]
2019-06-21 9:01 ` Daniel Vetter
2019-06-23 23:30 ` Laurent Pinchart
2019-06-24 8:19 ` Neil Armstrong
2019-06-24 8:42 ` Daniel Vetter
2019-06-24 11:16 ` Laurent Pinchart
2019-06-24 15:27 ` Andrzej Hajda
2019-09-18 8:05 ` Neil Armstrong
2019-09-18 16:39 ` Jonas Karlman
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=085dc3be-20e5-b2fe-4c02-bf4a4d1473da@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@bootlin.com \
--cc=wens@csie.org \
--cc=zhengyang@rock-chips.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