From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id DACE6E9B36F for ; Mon, 2 Mar 2026 12:36:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Type: Content-Transfer-Encoding:MIME-Version:References:In-Reply-To:Message-ID:Date :Subject:Cc:To:From:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=3BG6NbMJZCakv4h2SAqH1WDhyhJOxLlkoG0+u/X9t+w=; b=MGARSmpzS32FrvPduPMK2KAsRr 0wbSSK02rTK9RSkYK+6JppHmvOZBBzqx20+DLDgO0nXLF4PsY/FQNUtARfakSaDlupvVHX61BWf1q Yng5GXTJD/2T/FiIo63isdh2Yk8LWG3Gfc9Ke+iDWLZa1XwDCb4GF1G6XP7pczFQN21xsBydUXjdM vuzODnYIpHW8ibQYV3589O0t56Q03sXmx03HE1XGa9pgEnQHv8ws9gdDlWLNEa1nQrmq3gIrN9NnB h6uAgXZhbTzbp1aNaJKCKW2xp1vwHsGjMAWjxeck1Rk59kQJgu63uQ1MUut0Q9iuiilyJ4yrrJznI XEKO/YIA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1vx2VY-0000000Cztj-2jqR; Mon, 02 Mar 2026 12:36:20 +0000 Received: from sender4-pp-f112.zoho.com ([136.143.188.112]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1vx2VW-0000000Czt9-1zUw; Mon, 02 Mar 2026 12:36:19 +0000 ARC-Seal: i=1; a=rsa-sha256; t=1772454928; cv=none; d=zohomail.com; s=zohoarc; b=EdM6kuDOOrBMjnk82Ujo+bVjEAXNVDAZBqVU/C5AIUuCTCpiFxwCZcpe03EWauXknbjeD766XJC5tJXnzS73vS3HbLrIVgx4rI/i1umJU3RCWVf4cWtY31b9OEOnDlRP22zfC84VoMNE73XFwNmWC4jeftCBL06vVeerlFo1Mxg= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1772454928; h=Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=3BG6NbMJZCakv4h2SAqH1WDhyhJOxLlkoG0+u/X9t+w=; b=TiGFuMZyrE5Ol/sLoQp+n0ByX0Xz2NUfj2Wbg/OGQXHHc+WHNgMxrth2sK/DXaQUgopkpXqtj73ZFd4FpvtZVvJsUOXn5b909FImg8PufyEmX3POJt6RtJLYu6HzjrzyRCD24SyHVJo7YW4IT+h4B294hCJ/oza3vNm3PR0QHA8= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=collabora.com; spf=pass smtp.mailfrom=nicolas.frattaroli@collabora.com; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1772454928; s=zohomail; d=collabora.com; i=nicolas.frattaroli@collabora.com; h=From:From:To:To:Cc:Cc:Subject:Subject:Date:Date:Message-ID:In-Reply-To:References:MIME-Version:Content-Transfer-Encoding:Content-Type:Message-Id:Reply-To; bh=3BG6NbMJZCakv4h2SAqH1WDhyhJOxLlkoG0+u/X9t+w=; b=B7iz3Bd6S3S9gUGiY3IxUc2MxIUugQu7iDZrJ/yyGxTlAtxwtsUGr5Xe5CLIXEGc 4z1rqx/G6PEKW5Q98G92SaBOZWk7fscOfqGNo1g8UGj3WiRlrlT4fxUNnQkh/ltgEPS YLQ2mrmefuTXI3ooJRzKjrWdygiygyjjnqNTQ15g= Received: by mx.zohomail.com with SMTPS id 1772454925950111.09737166746925; Mon, 2 Mar 2026 04:35:25 -0800 (PST) From: Nicolas Frattaroli To: Dmitry Baryshkov Cc: Harry Wentland , Leo Li , Rodrigo Siqueira , Alex Deucher , Christian =?UTF-8?B?S8O2bmln?= , David Airlie , Simona Vetter , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Andrzej Hajda , Neil Armstrong , Robert Foss , Laurent Pinchart , Jonas Karlman , Jernej Skrabec , Sandy Huang , Heiko =?UTF-8?B?U3TDvGJuZXI=?= , Andy Yan , Jani Nikula , Rodrigo Vivi , Joonas Lahtinen , Tvrtko Ursulin , Dmitry Baryshkov , Sascha Hauer , Rob Herring , Jonathan Corbet , Shuah Khan , kernel@collabora.com, amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org, linux-doc@vger.kernel.org, Andri Yngvason , Werner Sembach , Marius Vlad Subject: Re: [PATCH v9 02/19] drm: Add new general DRM property "color format" Date: Mon, 02 Mar 2026 13:35:16 +0100 Message-ID: <5081457.31r3eYUQgx@workhorse> In-Reply-To: References: <20260227-color-format-v9-0-658c3b9db7ef@collabora.com> <20260227-color-format-v9-2-658c3b9db7ef@collabora.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260302_043618_543534_09C17AD7 X-CRM114-Status: GOOD ( 23.59 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Sunday, 1 March 2026 17:47:48 Central European Standard Time Dmitry Baryshkov wrote: > On Fri, Feb 27, 2026 at 08:20:07PM +0100, Nicolas Frattaroli wrote: > > From: Andri Yngvason > > > > Add a new general DRM property named "color format" which can be used by > > userspace to request the display driver to output a particular color > > format. > > > > Possible options are: > > - auto (setup by default, driver internally picks the color format) > > - rgb > > - ycbcr444 > > - ycbcr422 > > - ycbcr420 > > > > Drivers should advertise from this list which formats they support. > > Together with this list and EDID data from the sink we should be able > > to relay a list of usable color formats to users to pick from. > > > > Signed-off-by: Werner Sembach > > Signed-off-by: Andri Yngvason > > Signed-off-by: Marius Vlad > > Signed-off-by: Nicolas Frattaroli > > --- > > drivers/gpu/drm/drm_atomic_helper.c | 5 ++ > > drivers/gpu/drm/drm_atomic_uapi.c | 11 ++++ > > drivers/gpu/drm/drm_connector.c | 124 ++++++++++++++++++++++++++++++++++++ > > include/drm/drm_connector.h | 103 ++++++++++++++++++++++++++++++ > > 4 files changed, 243 insertions(+) > > It seems and feels that the common code to be used (almost?) everywhere > would be: > > if (!drm_mode_create_color_format_property(connector, supported_formats)) > drm_connector_attach_color_format_property(connector); > > > Please mention somewhere the reason to split that into two functions. > There isn't one I can think of, I kept it as-is since I inherited the code like this and figured this was the expected convention based on drm_mode_create_hdmi_colorspace_property -> drm_connector_attach_colorspace_property. Quite possibly, the idea is that callers can choose to probe whether a certain set of parameters would allow the property to be created without attaching it during said probing, but that's speculation on my part. Having it work like drm_connector_attach_max_bpc_property may make more sense here, and I'll refactor it to do this in the next revision unless anyone has any objections. Kind regards, Nicolas Frattaroli