From: Louis Chauvet <louis.chauvet@bootlin.com>
To: Luca Ceresoli <luca.ceresoli@bootlin.com>,
Haneen Mohammed <hamohammed.sa@gmail.com>,
Simona Vetter <simona@ffwll.ch>,
Melissa Wen <melissa.srw@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
jose.exposito89@gmail.com, Jonathan Corbet <corbet@lwn.net>
Cc: victoria@system76.com, sebastian.wick@redhat.com,
thomas.petazzoni@bootlin.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH RESEND v2 15/32] drm/vkms: Introduce configfs for plane color range
Date: Fri, 19 Dec 2025 17:55:19 +0100 [thread overview]
Message-ID: <5eeedbf9-7ca0-4e5b-9db0-616866af4ac8@bootlin.com> (raw)
In-Reply-To: <DF1JETBGEUFA.EK2SDN9BJMB6@bootlin.com>
On 12/18/25 19:00, Luca Ceresoli wrote:
> On Wed Oct 29, 2025 at 3:36 PM CET, Louis Chauvet wrote:
>> To allows the userspace to test many hardware configuration, introduce a
>> new interface to configure the available color ranges per planes. VKMS
>> supports multiple color ranges, so the userspace can choose any
>> combination.
>>
>> The supported color ranges are configured by writing a color range bitmask
>> to the file `supported_color_ranges` and the default color range is
>> chosen by writing a color encoding bitmask to `default_color_range`.
>>
>> Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
>
>> diff --git a/drivers/gpu/drm/vkms/vkms_configfs.c b/drivers/gpu/drm/vkms/vkms_configfs.c
>> index ee2e8d141f9e..3f658dd41272 100644
>> --- a/drivers/gpu/drm/vkms/vkms_configfs.c
>> +++ b/drivers/gpu/drm/vkms/vkms_configfs.c
>> @@ -439,6 +439,91 @@ static ssize_t plane_default_rotation_store(struct config_item *item,
>> return count;
>> }
>>
>> +static ssize_t plane_supported_color_ranges_show(struct config_item *item, char *page)
>> +{
>> + struct vkms_configfs_plane *plane;
>> + unsigned int supported_color_range;
> supported_color_ranges
>
>> +
>> + plane = plane_item_to_vkms_configfs_plane(item);
>
> As for previous patches, set this on declaration for consistency (same below).
>
>> +static ssize_t plane_supported_color_ranges_store(struct config_item *item,
>> + const char *page, size_t count)
>> +{
>> + struct vkms_configfs_plane *plane = plane_item_to_vkms_configfs_plane(item);
>> + int ret, val = 0;
>> +
>> + ret = kstrtouint(page, 10, &val);
>> + if (ret)
>> + return ret;
>> +
>> + /* Should be a supported value */
>> + if (val & ~(BIT(DRM_COLOR_YCBCR_LIMITED_RANGE) |
>> + BIT(DRM_COLOR_YCBCR_FULL_RANGE)))
>> + return -EINVAL;
>> + /* Should at least provide one color range */
>> + if ((val & (BIT(DRM_COLOR_YCBCR_LIMITED_RANGE) |
>> + BIT(DRM_COLOR_YCBCR_FULL_RANGE))) == 0)
>> + return -EINVAL;
>> +
>> + scoped_guard(mutex, &plane->dev->lock) {
>> + /* Ensures that the default rotation is included in supported rotation */
>
> Oh no, that comment again! :-)
>
>> +static ssize_t plane_default_color_range_store(struct config_item *item,
>> + const char *page, size_t count)
>> +{
>> + struct vkms_configfs_plane *plane = plane_item_to_vkms_configfs_plane(item);
>> + int ret, val = 0;
>> +
>> + ret = kstrtouint(page, 10, &val);
>> + if (ret)
>> + return ret;
>> +
>> + /* Should be a supported value */
>> + if (val & ~(BIT(DRM_COLOR_YCBCR_LIMITED_RANGE) |
>> + BIT(DRM_COLOR_YCBCR_FULL_RANGE)))
>> + return -EINVAL;
>> + /* Should at least provide one color range */
>> + if ((val & (BIT(DRM_COLOR_YCBCR_LIMITED_RANGE) |
>> + BIT(DRM_COLOR_YCBCR_FULL_RANGE))) == 0)
>> + return -EINVAL;
>
> As in patch 12, replace this with is_power_of_2() to check that exactly one
> bit is set.
And as the previous patch, this code is simply wrong...
I shoud check if val is one of DRM_COLOR_YCBCR_LIMITED_RANGE /
DRM_COLOR_YCBCR_FULL_RANGE
Thanks
> Luca
>
> --
> Luca Ceresoli, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
next prev parent reply other threads:[~2025-12-19 16:55 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 14:36 [PATCH RESEND v2 00/32] VKMS: Introduce multiple configFS attributes Louis Chauvet
2025-10-29 14:36 ` [PATCH RESEND v2 01/32] drm/drm_mode_config: Add helper to get plane type name Louis Chauvet
2025-11-13 14:06 ` José Expósito
2025-11-17 11:28 ` Louis Chauvet
2025-12-18 17:56 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 02/32] drm/vkms: Explicitly display plane type Louis Chauvet
2025-11-13 14:07 ` José Expósito
2025-12-18 17:56 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 03/32] drm/vkms: Use enabled/disabled instead of 1/0 for debug Louis Chauvet
2025-11-13 14:09 ` José Expósito
2025-12-18 17:57 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 04/32] drm/vkms: Explicitly display connector status Louis Chauvet
2025-11-13 14:11 ` José Expósito
2025-12-18 17:56 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 05/32] drm/vkms: Introduce config for plane name Louis Chauvet
2025-11-13 14:17 ` José Expósito
2025-11-17 14:12 ` Louis Chauvet
2025-10-29 14:36 ` [PATCH RESEND v2 06/32] drm/vkms: Introduce configfs " Louis Chauvet
2025-11-13 14:21 ` José Expósito
2025-11-17 9:56 ` Louis Chauvet
2025-12-18 17:58 ` Luca Ceresoli
2025-12-19 15:49 ` Louis Chauvet
2025-10-29 14:36 ` [PATCH RESEND v2 07/32] drm/blend: Get a rotation name from it's bitfield Louis Chauvet
2025-11-13 14:23 ` José Expósito
2025-12-18 17:58 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 08/32] drm/vkms: Introduce config for plane rotation Louis Chauvet
2025-12-18 17:59 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 09/32] drm/vkms: Introduce configfs " Louis Chauvet
2025-12-18 17:59 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 10/32] drm/drm_color_mgmt: Expose drm_get_color_encoding_name Louis Chauvet
2025-12-18 17:59 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 11/32] drm/vkms: Introduce config for plane color encoding Louis Chauvet
2025-12-18 17:59 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 12/32] drm/vkms: Introduce configfs " Louis Chauvet
2025-12-18 17:59 ` Luca Ceresoli
2025-12-19 16:40 ` Louis Chauvet
2025-12-19 17:51 ` Louis Chauvet
2025-10-29 14:36 ` [PATCH RESEND v2 13/32] drm/drm_color_mgmt: Expose drm_get_color_range_name Louis Chauvet
2025-12-18 17:59 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 14/32] drm/vkms: Introduce config for plane color range Louis Chauvet
2025-12-18 17:59 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 15/32] drm/vkms: Introduce configfs " Louis Chauvet
2025-12-18 18:00 ` Luca Ceresoli
2025-12-19 16:55 ` Louis Chauvet [this message]
2025-10-29 14:36 ` [PATCH RESEND v2 16/32] drm/vkms: Introduce config for plane format Louis Chauvet
2025-12-19 14:55 ` Luca Ceresoli
2025-12-19 18:31 ` Louis Chauvet
2025-10-29 14:36 ` [PATCH RESEND v2 17/32] drm/vkms: Introduce configfs " Louis Chauvet
2025-12-19 17:07 ` Luca Ceresoli
2025-12-19 17:28 ` Louis Chauvet
2025-10-29 14:36 ` [PATCH RESEND v2 18/32] drm/vkms: Properly render plane using their zpos Louis Chauvet
2025-12-19 17:08 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 19/32] drm/vkms: Introduce config for plane zpos property Louis Chauvet
2025-12-19 17:08 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 20/32] drm/vkms: Introduce configfs " Louis Chauvet
2025-12-19 17:08 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 21/32] drm/vkms: Introduce config for connector type Louis Chauvet
2025-12-19 17:08 ` Luca Ceresoli
2025-10-29 14:36 ` [PATCH RESEND v2 22/32] drm/vkms: Introduce configfs " Louis Chauvet
2025-12-19 17:08 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 23/32] drm/connector: Export drm_get_colorspace_name Louis Chauvet
2025-12-19 17:08 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 24/32] drm/vkms: Introduce config for connector supported colorspace Louis Chauvet
2025-12-19 17:08 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 25/32] drm/vkms: Introduce configfs " Louis Chauvet
2025-12-19 18:56 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 26/32] drm/vkms: Introduce config for connector EDID Louis Chauvet
2025-12-19 18:56 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 27/32] drm/vkms: Introduce configfs " Louis Chauvet
2025-12-19 18:56 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 28/32] drm/vkms: Store the enabled/disabled status for connector Louis Chauvet
2025-12-19 18:57 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 29/32] drm/vkms: Rename vkms_connector_init to vkms_connector_init_static Louis Chauvet
2025-12-19 18:58 ` Luca Ceresoli
2025-12-19 19:11 ` Louis Chauvet
2025-12-19 20:47 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 30/32] drm/vkms: Extract common code for connector initialization Louis Chauvet
2025-12-19 20:47 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 31/32] drm/vkms: Allow to hot-add connectors Louis Chauvet
2025-12-19 20:47 ` Luca Ceresoli
2025-10-29 14:37 ` [PATCH RESEND v2 32/32] drm/vkms: Introduce configfs for dynamic connector creation Louis Chauvet
2025-12-19 20:47 ` Luca Ceresoli
2025-12-19 22:01 ` Louis Chauvet
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=5eeedbf9-7ca0-4e5b-9db0-616866af4ac8@bootlin.com \
--to=louis.chauvet@bootlin.com \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=jose.exposito89@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=sebastian.wick@redhat.com \
--cc=simona@ffwll.ch \
--cc=thomas.petazzoni@bootlin.com \
--cc=tzimmermann@suse.de \
--cc=victoria@system76.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