public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Jonas Karlman <jonas@kwiboo.se>
Cc: "a.hajda@samsung.com" <a.hajda@samsung.com>,
	"Laurent.pinchart@ideasonboard.com" 
	<Laurent.pinchart@ideasonboard.com>,
	"jernej.skrabec@siol.net" <jernej.skrabec@siol.net>,
	"narmstrong@baylibre.com" <narmstrong@baylibre.com>,
	"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>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] drm/rockchip: Enable DRM InfoFrame support on RK3328 and RK3399
Date: Fri, 14 Jun 2019 11:29:33 +0200	[thread overview]
Message-ID: <4131981.039HHiXCja@phil> (raw)
In-Reply-To: <VI1PR03MB42062F51FD88AEB6DADD8734AC1C0@VI1PR03MB4206.eurprd03.prod.outlook.com>

Am Sonntag, 26. Mai 2019, 23:20:05 CEST schrieb Jonas Karlman:
> This patch enables Dynamic Range and Mastering InfoFrame on RK3328 and RK3399.
> 
> Cc: Sandy Huang <hjc@rock-chips.com>
> Cc: Heiko Stuebner <heiko@sntech.de>
> Signed-off-by: Jonas Karlman <jonas@kwiboo.se>

Reviewed-by: Heiko Stuebner <heiko@sntech.de>

> ---
>  drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c b/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
> index 4cdc9f86c2e5..1f31f3726f04 100644
> --- a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
> +++ b/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
> @@ -405,6 +405,7 @@ static const struct dw_hdmi_plat_data rk3328_hdmi_drv_data = {
>  	.phy_ops = &rk3328_hdmi_phy_ops,
>  	.phy_name = "inno_dw_hdmi_phy2",
>  	.phy_force_vendor = true,
> +	.drm_infoframe = true,
>  };
>  
>  static struct rockchip_hdmi_chip_data rk3399_chip_data = {
> @@ -419,6 +420,7 @@ static const struct dw_hdmi_plat_data rk3399_hdmi_drv_data = {
>  	.cur_ctr    = rockchip_cur_ctr,
>  	.phy_config = rockchip_phy_config,
>  	.phy_data = &rk3399_chip_data,
> +	.drm_infoframe = true,
>  };
>  
>  static const struct of_device_id dw_hdmi_rockchip_dt_ids[] = {
> -- 
> 2.17.1
> 
> 





  reply	other threads:[~2019-06-14  9:29 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 [this message]
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
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=4131981.039HHiXCja@phil \
    --to=heiko@sntech.de \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=a.hajda@samsung.com \
    --cc=dri-devel@lists.freedesktop.org \
    --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=narmstrong@baylibre.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