Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp2169786ybd; Mon, 24 Jun 2019 01:53:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqymSKWwZ2cLk35phpR5hCwQRrzRAdZzSwBXdJPlaTkogJOQWJPoVbhiLIutEODUyZeBQuVr X-Received: by 2002:a17:90a:cb87:: with SMTP id a7mr24232737pju.130.1561366412428; Mon, 24 Jun 2019 01:53:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561366412; cv=none; d=google.com; s=arc-20160816; b=Hh00IvIzSQIXY9Uq/EHN1QA8yoQqMUPytuxVWAUtJSnC30Zh4Ajj7nnyeY9ym+AfWC xuv19WtMzpMT5kIO7GAVT6CvZnSg6VrgHUhQE3yPpN0MgtzQQOvRvanbaApeMgJfFn/9 aQ7LN0/79sl314hGmGN1E6Q0XS7MpAdi/d244y6qEKk6v3swiG/M3HFrJljewM7SQRvj yUEJAehm7cWxpwPY1Kymf2SsjCb7FNYt/xxW9IUCUbcDosVRHnXOrdI5BF+GG7nGvxpy N/2XCN2LQ5jAaEoVk3KZDpKKHlveppmPTPonvPovgN3qFq31agbTVrCIhdxN4OzBZchp nVPg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:cc:to:from:date:dkim-signature; bh=X9V0I0rT3Iuwr77W2nr5FjsCxhtOBnuvS2mOp7LZweg=; b=zMscum3cYUX8+YqUT8Z4cqkHsYMmQE2p8liS0xpXoAc/1D0JM9AOUTMuREXeOfV/65 EGD2KCLjuYYRg6FIm5IQqqtQhwjQasuPsA9VDZBJ4qZ79WqyWCwI5fFszcIOSTptb/WK fB63yaUuYA8exUqijWDjzx1AHcMnV8WJT2gIIMCHeRWNxKkStD3dSkr9+SOz/5q9KuKY yvVQGTYPEOy4/ODpzQAhVisDISq12c1U8faVGPDaeEipTylefj/c6l2ce1Hyyb2XPG56 8s14yPk6i0dpcBu61Dql0U7LspTEqIz2HpuJViFDYTNCFb2GUjQe2ZYWGZicFO3zeNfT EGqQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@ffwll.ch header.s=google header.b=H6hDKzNt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t64si8336071pgd.126.2019.06.24.01.53.16; Mon, 24 Jun 2019 01:53:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@ffwll.ch header.s=google header.b=H6hDKzNt; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727709AbfFXIml (ORCPT + 99 others); Mon, 24 Jun 2019 04:42:41 -0400 Received: from mail-ed1-f68.google.com ([209.85.208.68]:39180 "EHLO mail-ed1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726885AbfFXImk (ORCPT ); Mon, 24 Jun 2019 04:42:40 -0400 Received: by mail-ed1-f68.google.com with SMTP id m10so20581946edv.6 for ; Mon, 24 Jun 2019 01:42:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=X9V0I0rT3Iuwr77W2nr5FjsCxhtOBnuvS2mOp7LZweg=; b=H6hDKzNtCd7adLn/KUBkZ0Uf2qlQpq1e/fO+KMsRaIbR2iE4bsUAvqEWLCCKkI31mH YP899xwf3+kMbVMVar5LTtE7bcbyuc0PfsTEJY5W1Eky85kgxv7nHvMGPjLYXxRqmfKB YQEWgFzlolfDhKKUejA5VspYHSu33zngw0UEI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=X9V0I0rT3Iuwr77W2nr5FjsCxhtOBnuvS2mOp7LZweg=; b=R0cXhYZuFS4nPudFLTij6cDagROi60AWLlQV7rqtOYRsVKj0u+nkH2KJpAyhtg23L8 v5s/8iXSE6souAaQYivXy7kixNoCdMLPmsYs49EQhjWcttNyc1aRMFXunr0aOhchpyNx i3TtEK2Aq1NdcFAWSuh+iQB5ebThzKkvZy1bOytsGO6G3GJMzS6hnH1YH4XFXCa7EuPi lGzi0LFimlus0JyvAB+AlkVshmoido9Ra8A4Kb9OiVTPBOaipMICObb4HPO6yJL6XmWe wiZa61zR3nE3hsTfG8XYGt4vgLzCt5jzMW+udI3UDsTYdv8vo9LcN5gNp8/Y/7LbkjTA CbKg== X-Gm-Message-State: APjAAAXCUKFzFFuKeXKqJzIVl7WKb+XHZxlX7wV61ti36qmdqNmV5OyA kl4wjUsTySfRaIVPWNk4xdHClA== X-Received: by 2002:a17:906:d797:: with SMTP id pj23mr80092489ejb.223.1561365758561; Mon, 24 Jun 2019 01:42:38 -0700 (PDT) Received: from phenom.ffwll.local ([2a02:168:569e:0:3106:d637:d723:e855]) by smtp.gmail.com with ESMTPSA id l10sm1778061ejh.53.2019.06.24.01.42.37 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 24 Jun 2019 01:42:37 -0700 (PDT) Date: Mon, 24 Jun 2019 10:42:35 +0200 From: Daniel Vetter To: Neil Armstrong Cc: Laurent Pinchart , Jonas Karlman , "a.hajda@samsung.com" , "jernej.skrabec@siol.net" , "maxime.ripard@bootlin.com" , Daniel Vetter , "khilman@baylibre.com" , "dri-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , "wens@csie.org" , "zhengyang@rock-chips.com" Subject: Re: [PATCH 0/4] drm/bridge: dw-hdmi: Add support for HDR metadata Message-ID: <20190624084235.GN12905@phenom.ffwll.local> Mail-Followup-To: Neil Armstrong , Laurent Pinchart , Jonas Karlman , "a.hajda@samsung.com" , "jernej.skrabec@siol.net" , "maxime.ripard@bootlin.com" , "khilman@baylibre.com" , "dri-devel@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , "wens@csie.org" , "zhengyang@rock-chips.com" References: <085dc3be-20e5-b2fe-4c02-bf4a4d1473da@baylibre.com> <20190621090125.GX12905@phenom.ffwll.local> <20190623233017.GI6124@pendragon.ideasonboard.com> <58243243-fbd8-e67b-a050-baa9757be43e@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <58243243-fbd8-e67b-a050-baa9757be43e@baylibre.com> X-Operating-System: Linux phenom 4.19.0-5-amd64 User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 24, 2019 at 10:19:34AM +0200, Neil Armstrong wrote: > Hi Daniel, Laurent, Andrzej, > > On 24/06/2019 01:30, Laurent Pinchart wrote: > > On Fri, Jun 21, 2019 at 11:01:25AM +0200, Daniel Vetter wrote: > >> On Thu, Jun 20, 2019 at 04:40:12PM +0200, Neil Armstrong wrote: > >>> Hi Andrzej, > >>> > >>> Gentle ping, could you review the dw-hdmi changes here ? > >> > >> btw not sure you absolutely need review from Andrzej, we're currently a > >> bit undersupplied with bridge reviewers I think ... Better to ramp up > >> more. > > > > I try to review DRM bridge patches when possible, but dw-hdmi is a > > special case. I was told by the supplier of an SoC datasheet that > > contains the HDMI encoder IP core documentation that Synopsys required > > them to route all contributions made based on that documentation through > > Synopsys' internal legal review before publishing them. I thus decided > > to not contribute to the driver anymore, at least for areas that require > > access to documentation. > > I'd like to propose myself as co-maintainer of the DRM bridge subsystem if > everybody agrees, following the excellent work Laurent and Andrzej did. > I have a very little knowledge of DSI, & other bridge drivers, but I'll do > my best. Yay volunteers! Make MAINTAINERS patch to add you, cc relevant people, get acks, merge, tag you're it :-) Ok, co-it, the point is to have teams as much as possible. Cheers, Daniel > > For the dw-hdmi driver, we have a big roadmap including : > - HDR (this patchset) > - HDCP 1/2 > - YUV420, YUV422, YUV44, 10bit/12bit/16bit HDMI output > - Enhanced audio support and ELD notification to ASoC > ... > > Having a more active maintainer/reviewer team would be needed, at least for > the dw-hdmi bridge. > > I'll also propose Jonas Karlman as reviewer since he is very > active for the multimedia support on RockChip, Allwinner and Amlogic SoCs. > I'll also propose Jernej Skrabec@siol.net , if he wants, > as reviewer since he is very active on the Allwinner SoCs side. > > 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(+) > > > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch