[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8b45942a-c0e6-4f14-9df6-76a50e507b87@riseup.net>
Date: Mon, 28 Oct 2024 07:39:08 -0300
From: Maíra Canal <mairacanal@...eup.net>
To: Rodrigo Siqueira <rodrigosiqueiramelo@...il.com>,
Melissa Wen <melissa.srw@...il.com>,
Haneen Mohammed <hamohammed.sa@...il.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>,
Simona Vetter <simona.vetter@...ll.ch>, dri-devel@...ts.freedesktop.org,
arthurgrillo@...eup.net, linux-kernel@...r.kernel.org,
jeremie.dautheribes@...tlin.com, miquel.raynal@...tlin.com,
thomas.petazzoni@...tlin.com, seanpaul@...gle.com, marcheu@...gle.com,
nicolejadeyee@...gle.com, 20241007-yuv-v12-0-01c1ada6fec8@...tlin.com
Subject: Re: [PATCH RESEND v2 5/8] drm/vkms: Add support for RGB888 formats
Hi Louis,
On 28/10/24 06:50, Louis Chauvet wrote:
> On 26/10/24 - 11:51, Maíra Canal wrote:
>> Hi Louis,
>>
>> On 07/10/24 13:46, Louis Chauvet wrote:
>>> Add the support for:
>>> - RGB888
>>> - BGR888
>>>
>>> Signed-off-by: Louis Chauvet <louis.chauvet@...tlin.com>
>>> ---
>>> drivers/gpu/drm/vkms/vkms_formats.c | 7 +++++++
>>> drivers/gpu/drm/vkms/vkms_plane.c | 2 ++
>>> 2 files changed, 9 insertions(+)
>>>
>>> diff --git a/drivers/gpu/drm/vkms/vkms_formats.c b/drivers/gpu/drm/vkms/vkms_formats.c
>>> index e34bea5da752..2376ea8661ac 100644
>>> --- a/drivers/gpu/drm/vkms/vkms_formats.c
>>> +++ b/drivers/gpu/drm/vkms/vkms_formats.c
>>> @@ -461,6 +461,9 @@ READ_LINE_ARGB8888(ABGR8888_read_line, px, px[3], px[0], px[1], px[2])
>>> READ_LINE_ARGB8888(RGBA8888_read_line, px, px[0], px[3], px[2], px[1])
>>> READ_LINE_ARGB8888(BGRA8888_read_line, px, px[0], px[1], px[2], px[3])
>>> +READ_LINE_ARGB8888(RGB888_read_line, px, 255, px[2], px[1], px[0])
>>> +READ_LINE_ARGB8888(BGR888_read_line, px, 255, px[0], px[1], px[2])
>>> +
>>> READ_LINE_16161616(ARGB16161616_read_line, px, px[3], px[2], px[1], px[0])
>>> READ_LINE_16161616(ABGR16161616_read_line, px, px[3], px[0], px[1], px[2])
>>> READ_LINE_16161616(XRGB16161616_read_line, px, 0xFFFF, px[2], px[1], px[0])
>>> @@ -679,6 +682,10 @@ pixel_read_line_t get_pixel_read_line_function(u32 format)
>>> return &RGBX8888_read_line;
>>> case DRM_FORMAT_BGRX8888:
>>> return &BGRX8888_read_line;
>>> + case DRM_FORMAT_RGB888:
>>> + return RGB888_read_line;
>>
>> Shouldn't it be &RGB888_read_line?
>
> According to [1], &function, function, ***function are understood the
> same by gcc.
>
> But this is ugly and I will change to use & everywhere, thanks!
I didn't know that, that's interesting. I'd add & just for consistency.
Best Regards,
- Maíra
>
> [1]:https://stackoverflow.com/questions/6893285/why-do-function-pointer-definitions-work-with-any-number-of-ampersands-or-as
>
> Thanks,
> Louis Chauvet
>
>>> + case DRM_FORMAT_BGR888:
>>> + return BGR888_read_line;
>>
>> Same.
>>
>> Best Regards,
>> - Maíra
>>
>>> case DRM_FORMAT_ARGB16161616:
>>> return &ARGB16161616_read_line;
>>> case DRM_FORMAT_ABGR16161616:
>>> diff --git a/drivers/gpu/drm/vkms/vkms_plane.c b/drivers/gpu/drm/vkms/vkms_plane.c
>>> index a243a706459f..0fa589abc53a 100644
>>> --- a/drivers/gpu/drm/vkms/vkms_plane.c
>>> +++ b/drivers/gpu/drm/vkms/vkms_plane.c
>>> @@ -21,6 +21,8 @@ static const u32 vkms_formats[] = {
>>> DRM_FORMAT_XBGR8888,
>>> DRM_FORMAT_RGBX8888,
>>> DRM_FORMAT_BGRX8888,
>>> + DRM_FORMAT_RGB888,
>>> + DRM_FORMAT_BGR888,
>>> DRM_FORMAT_XRGB16161616,
>>> DRM_FORMAT_XBGR16161616,
>>> DRM_FORMAT_ARGB16161616,
>>>
Powered by blists - more mailing lists