[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02da12fe-4d94-4a40-86b6-6dad28588843@ideasonboard.com>
Date: Wed, 18 Dec 2024 13:49:01 +0200
From: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
To: "Sagar, Vishal" <vishal.sagar@....com>
Cc: "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"Klymenko, Anatoliy" <Anatoliy.Klymenko@....com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
"Simek, Michal" <michal.simek@....com>
Subject: Re: [PATCH 01/10] drm/fourcc: Add warning for bad bpp
Hi Vishal,
On 04/12/2024 18:26, Sagar, Vishal wrote:
> [AMD Official Use Only - AMD Internal Distribution Only]
>
> Hi Tomi,
>
> Thanks for the patch.
>
>> -----Original Message-----
>> From: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
>> Sent: Wednesday, December 4, 2024 10:31 AM
>> To: Sagar, Vishal <vishal.sagar@....com>; Klymenko, Anatoliy
>> <Anatoliy.Klymenko@....com>; Maarten Lankhorst
>> <maarten.lankhorst@...ux.intel.com>; Maxime Ripard <mripard@...nel.org>;
>> Thomas Zimmermann <tzimmermann@...e.de>; David Airlie
>> <airlied@...il.com>; Simona Vetter <simona@...ll.ch>; Laurent Pinchart
>> <laurent.pinchart@...asonboard.com>; Simek, Michal <michal.simek@....com>
>> Cc: dri-devel@...ts.freedesktop.org; linux-kernel@...r.kernel.org; linux-arm-
>> kernel@...ts.infradead.org; Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
>> Subject: [PATCH 01/10] drm/fourcc: Add warning for bad bpp
>>
>> drm_format_info_bpp() cannot be used for formats which do not have an
>> integer bits-per-pixel. Handle wrong calls by printing a warning and
>> returning 0.
>
> It would be good to add an example of pixel format that may cause this issue.
Indeed, the description is perhaps a bit lacking. I'll change it to:
drm_format_info_bpp() cannot be used for formats which do not have an
integer bits-per-pixel in a pixel block.
E.g. DRM_FORMAT_XV15's (not yet in upstream) plane 0 has three 10-bit
pixels (Y components), and two padding bits, in a 4 byte block. That is
10.666... bits per pixel when considering the whole 4 byte block, which
is what drm_format_info_bpp() does. Thus a driver that supports such
formats cannot use drm_format_info_bpp(),
It is a driver bug if this happens, but so handle wrong calls by
printing a warning and returning 0.
Tomi
>>
>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
>> ---
>> drivers/gpu/drm/drm_fourcc.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/drm_fourcc.c b/drivers/gpu/drm/drm_fourcc.c
>> index 193cf8ed7912..e84c4ed6928c 100644
>> --- a/drivers/gpu/drm/drm_fourcc.c
>> +++ b/drivers/gpu/drm/drm_fourcc.c
>> @@ -429,6 +429,13 @@ unsigned int drm_format_info_bpp(const struct
>> drm_format_info *info, int plane)
>> if (!info || plane < 0 || plane >= info->num_planes)
>> return 0;
>>
>> + if (info->char_per_block[plane] * 8 %
>> + (drm_format_info_block_width(info, plane) *
>> + drm_format_info_block_height(info, plane))) {
>> + pr_warn("unable to return an integer bpp\n");
>> + return 0;
>> + }
>> +
>> return info->char_per_block[plane] * 8 /
>> (drm_format_info_block_width(info, plane) *
>> drm_format_info_block_height(info, plane));
>>
>> --
>> 2.43.0
>
> Regards
> Vishal Sagar
Powered by blists - more mailing lists