Received: by 2002:a05:7412:e794:b0:fa:551:50a7 with SMTP id o20csp990029rdd; Wed, 10 Jan 2024 05:42:04 -0800 (PST) X-Google-Smtp-Source: AGHT+IEi5Tm4D1sPfFdubYKjBNGnHkV12AD3EzQSaVKPSdF1cXZGmPPOvVz4FTgdNmEqLIlqKDWq X-Received: by 2002:a05:6e02:16c7:b0:360:746d:96b5 with SMTP id 7-20020a056e0216c700b00360746d96b5mr1329309ilx.35.1704894124558; Wed, 10 Jan 2024 05:42:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704894124; cv=none; d=google.com; s=arc-20160816; b=YjnikD6HCYxoUjpzjq7a+YYiAIJrIhW6QAvfqlNRjNUxo+xRqJ2tNY3w1gOPEgieke +SyzA9rV6r68X+wbum04kVewqgDgTCp44kPcm8Af6+Eww7DuwyAszWI7lSC5hF5FS4ex k/l6++4OwnV5UAUMATV723LMRTEkzOkjEzyyMgFI9RnG3YIzWQsXhp0+yQUnHpw5eISf k9ReqU/TqB3Bxpc56Gf/oF1uEiCz8SG6Jn9qBEXvkRexGt3EKQgTK11U2paIaVTEyft0 LvJdTudbHdeHbYPAU920vlPwBAZosXzAIQdTqFAQKTndVFr3Pz/AbowEUyT0yNyQ0V/d pvhg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:date:message-id:dkim-signature; bh=NBr8Ca6T6pj462sAdOhvmla4yehDm43kFrOCFOhWR1Y=; fh=6IJNWhWXbiSWIpFNvvynOgz0lyaPC8hk6uB2aMeO0bs=; b=j0hquPsQJ99AZwQH9NOTGMC4NvibIMFoj6Bmxp0dWK4rnqSF2jzDyh8tXIbz6MRuxw FoNIRlphmt41Ges1h7tNeW7ofSbeXBf8dLLgDj1GQ11zVpN/qXco8oMTArfZnstj1XVN Re/OZcgEwb0kgv0dAsa1/tK2uSbyu7j6LJmND0+QRgHBiWsEeIc08SgZp/cVXlefMBYu FerF1fQ5SQduByAI+Dfuz3mzeRH6ZXu0E3Z/rGaG2TX6gGxYMYQgSmYEWu7LDQHP9iTp fAxsyZafbBrUI3lRFHoxiYiS+LynEzEQPO/C+NvR39HeoiXX5mh1Us+XtN7AuoucZVWL 3fqg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@tuxedocomputers.com header.s=default header.b=gVo2F6g+; spf=pass (google.com: domain of linux-kernel+bounces-22259-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-22259-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=tuxedocomputers.com Return-Path: Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org. [147.75.48.161]) by mx.google.com with ESMTPS id w14-20020a63474e000000b005ce08f92a99si3494087pgk.151.2024.01.10.05.42.04 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 10 Jan 2024 05:42:04 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-22259-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161; Authentication-Results: mx.google.com; dkim=pass header.i=@tuxedocomputers.com header.s=default header.b=gVo2F6g+; spf=pass (google.com: domain of linux-kernel+bounces-22259-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-22259-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=tuxedocomputers.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id 17661B22904 for ; Wed, 10 Jan 2024 13:39:50 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id D5C4B48CD6; Wed, 10 Jan 2024 13:39:43 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=tuxedocomputers.com header.i=@tuxedocomputers.com header.b="gVo2F6g+" Received: from mail.tuxedocomputers.com (mail.tuxedocomputers.com [157.90.84.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 53643487BE for ; Wed, 10 Jan 2024 13:39:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=tuxedocomputers.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=tuxedocomputers.com Received: from [192.168.42.20] (p5de453e7.dip0.t-ipconnect.de [93.228.83.231]) (Authenticated sender: wse@tuxedocomputers.com) by mail.tuxedocomputers.com (Postfix) with ESMTPSA id B9B3D2FC0057; Wed, 10 Jan 2024 14:39:36 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tuxedocomputers.com; s=default; t=1704893977; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=NBr8Ca6T6pj462sAdOhvmla4yehDm43kFrOCFOhWR1Y=; b=gVo2F6g+ftVSYC2ja0jm3fxua0sVpmkTiKLfrSHyAOrY+XXctIu7qXUbkFlFlWXjqK/Fc1 uYJro0xKbuZckVlyENB1J8JodhKUWjW/2AtMfinRHk3eeTLCMWYQjowChFgzx4Fn/cXsD7 TYwdrGPxRaL43cqyTrME63S25KScnyE= Authentication-Results: mail.tuxedocomputers.com; auth=pass smtp.auth=wse@tuxedocomputers.com smtp.mailfrom=wse@tuxedocomputers.com Message-ID: Date: Wed, 10 Jan 2024 14:39:36 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 2/7] drm/uAPI: Add "active color format" drm property as feedback for userspace Content-Language: en-US To: Andri Yngvason , Harry Wentland , Leo Li , Rodrigo Siqueira , Alex Deucher , =?UTF-8?Q?Christian_K=C3=B6nig?= , "Pan, Xinhui" , David Airlie , Daniel Vetter , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Jani Nikula , Joonas Lahtinen , Rodrigo Vivi , Tvrtko Ursulin Cc: amd-gfx@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org References: <20240109181104.1670304-1-andri@yngvason.is> <20240109181104.1670304-3-andri@yngvason.is> From: Werner Sembach In-Reply-To: <20240109181104.1670304-3-andri@yngvason.is> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Hi, Am 09.01.24 um 19:10 schrieb Andri Yngvason: > From: Werner Sembach > > Add a new general drm property "active color format" which can be used by > graphic drivers to report the used color format back to userspace. > > There was no way to check which color format got actually used on a given > monitor. To surely predict this, one must know the exact capabilities of > the monitor, the GPU, and the connection used and what the default > behaviour of the used driver is (e.g. amdgpu prefers YCbCr 4:4:4 while i915 > prefers RGB). This property helps eliminating the guessing on this point. > > In the future, automatic color calibration for screens might also depend on > this information being available. > > Signed-off-by: Werner Sembach > Signed-off-by: Andri Yngvason > Tested-by: Andri Yngvason One suggestion from back then was, instead picking out singular properties like "active color format", to just expose whatever the last HDMI or DP metadata block(s)/frame(s) that was sent over the display wire was to userspace and accompanying it with a parsing script. Question: Does the driver really actually know what the GPU is ultimatively sending out the wire, or is that decided by a final firmware blob we have no info about? Greetings Werner > --- > drivers/gpu/drm/drm_connector.c | 63 +++++++++++++++++++++++++++++++++ > include/drm/drm_connector.h | 10 ++++++ > 2 files changed, 73 insertions(+) > > diff --git a/drivers/gpu/drm/drm_connector.c b/drivers/gpu/drm/drm_connector.c > index c3725086f4132..30d62e505d188 100644 > --- a/drivers/gpu/drm/drm_connector.c > +++ b/drivers/gpu/drm/drm_connector.c > @@ -1061,6 +1061,14 @@ static const struct drm_prop_enum_list drm_dp_subconnector_enum_list[] = { > { DRM_MODE_SUBCONNECTOR_Native, "Native" }, /* DP */ > }; > > +static const struct drm_prop_enum_list drm_active_color_format_enum_list[] = { > + { 0, "not applicable" }, > + { DRM_COLOR_FORMAT_RGB444, "rgb" }, > + { DRM_COLOR_FORMAT_YCBCR444, "ycbcr444" }, > + { DRM_COLOR_FORMAT_YCBCR422, "ycbcr422" }, > + { DRM_COLOR_FORMAT_YCBCR420, "ycbcr420" }, > +}; > + > DRM_ENUM_NAME_FN(drm_get_dp_subconnector_name, > drm_dp_subconnector_enum_list) > > @@ -1390,6 +1398,15 @@ static const u32 dp_colorspaces = > * drm_connector_attach_max_bpc_property() to create and attach the > * property to the connector during initialization. > * > + * active color format: > + * This read-only property tells userspace the color format actually used > + * by the hardware display engine "on the cable" on a connector. The chosen > + * value depends on hardware capabilities, both display engine and > + * connected monitor. Drivers shall use > + * drm_connector_attach_active_color_format_property() to install this > + * property. Possible values are "not applicable", "rgb", "ycbcr444", > + * "ycbcr422", and "ycbcr420". > + * > * Connectors also have one standardized atomic property: > * > * CRTC_ID: > @@ -2451,6 +2468,52 @@ int drm_connector_attach_max_bpc_property(struct drm_connector *connector, > } > EXPORT_SYMBOL(drm_connector_attach_max_bpc_property); > > +/** > + * drm_connector_attach_active_color_format_property - attach "active color format" property > + * @connector: connector to attach active color format property on. > + * > + * This is used to check the applied color format on a connector. > + * > + * Returns: > + * Zero on success, negative errno on failure. > + */ > +int drm_connector_attach_active_color_format_property(struct drm_connector *connector) > +{ > + struct drm_device *dev = connector->dev; > + struct drm_property *prop; > + > + if (!connector->active_color_format_property) { > + prop = drm_property_create_enum(dev, DRM_MODE_PROP_IMMUTABLE, "active color format", > + drm_active_color_format_enum_list, > + ARRAY_SIZE(drm_active_color_format_enum_list)); > + if (!prop) > + return -ENOMEM; > + > + connector->active_color_format_property = prop; > + } > + > + drm_object_attach_property(&connector->base, prop, 0); > + > + return 0; > +} > +EXPORT_SYMBOL(drm_connector_attach_active_color_format_property); > + > +/** > + * drm_connector_set_active_color_format_property - sets the active color format property for a > + * connector > + * @connector: drm connector > + * @active_color_format: color format for the connector currently active "on the cable" > + * > + * Should be used by atomic drivers to update the active color format over a connector. > + */ > +void drm_connector_set_active_color_format_property(struct drm_connector *connector, > + u32 active_color_format) > +{ > + drm_object_property_set_value(&connector->base, connector->active_color_format_property, > + active_color_format); > +} > +EXPORT_SYMBOL(drm_connector_set_active_color_format_property); > + > /** > * drm_connector_attach_hdr_output_metadata_property - attach "HDR_OUTPUT_METADA" property > * @connector: connector to attach the property on. > diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h > index fe88d7fc6b8f4..9ae73cfdceeb1 100644 > --- a/include/drm/drm_connector.h > +++ b/include/drm/drm_connector.h > @@ -1699,6 +1699,12 @@ struct drm_connector { > */ > struct drm_property *privacy_screen_hw_state_property; > > + /** > + * @active_color_format_property: Default connector property for the > + * active color format to be driven out of the connector. > + */ > + struct drm_property *active_color_format_property; > + > #define DRM_CONNECTOR_POLL_HPD (1 << 0) > #define DRM_CONNECTOR_POLL_CONNECT (1 << 1) > #define DRM_CONNECTOR_POLL_DISCONNECT (1 << 2) > @@ -2053,6 +2059,10 @@ void drm_connector_attach_privacy_screen_provider( > struct drm_connector *connector, struct drm_privacy_screen *priv); > void drm_connector_update_privacy_screen(const struct drm_connector_state *connector_state); > > +int drm_connector_attach_active_color_format_property(struct drm_connector *connector); > +void drm_connector_set_active_color_format_property(struct drm_connector *connector, > + u32 active_color_format); > + > /** > * struct drm_tile_group - Tile group metadata > * @refcount: reference count