On Wed, 28 Feb 2024 22:52:09 -0300
Arthur Grillo <arthurgrillo@xxxxxxxxxx> wrote:
> On 27/02/24 17:01, Arthur Grillo wrote:
> >
> >
> > On 27/02/24 12:02, Louis Chauvet wrote:
> >> Hi Pekka,
> >>
> >> For all the comment related to the conversion part, maybe Arthur have an
> >> opinion on it, I took his patch as a "black box" (I did not want to
> >> break (and debug) it).
> >>
> >> Le 26/02/24 - 14:19, Pekka Paalanen a écrit :
> >>> On Fri, 23 Feb 2024 12:37:26 +0100
> >>> Louis Chauvet <louis.chauvet@xxxxxxxxxxx> wrote:
> >>>
> >>>> From: Arthur Grillo <arthurgrillo@xxxxxxxxxx>
> >>>>
> >>>> Add support to the YUV formats bellow:
> >>>>
> >>>> - NV12
> >>>> - NV16
> >>>> - NV24
> >>>> - NV21
> >>>> - NV61
> >>>> - NV42
> >>>> - YUV420
> >>>> - YUV422
> >>>> - YUV444
> >>>> - YVU420
> >>>> - YVU422
> >>>> - YVU444
> >>>>
> >>>> The conversion matrices of each encoding and range were obtained by
> >>>> rounding the values of the original conversion matrices multiplied by
> >>>> 2^8. This is done to avoid the use of fixed point operations.
> >>>>
> >>>> Signed-off-by: Arthur Grillo <arthurgrillo@xxxxxxxxxx>
> >>>> [Louis Chauvet: Adapted Arthur's work and implemented the read_line_t
> >>>> callbacks for yuv formats]
> >>>> Signed-off-by: Louis Chauvet <louis.chauvet@xxxxxxxxxxx>
> >>>> ---
> >>>> drivers/gpu/drm/vkms/vkms_composer.c | 2 +-
> >>>> drivers/gpu/drm/vkms/vkms_drv.h | 6 +-
> >>>> drivers/gpu/drm/vkms/vkms_formats.c | 289 +++++++++++++++++++++++++++++++++--
> >>>> drivers/gpu/drm/vkms/vkms_formats.h | 4 +
> >>>> drivers/gpu/drm/vkms/vkms_plane.c | 14 +-
> >>>> 5 files changed, 295 insertions(+), 20 deletions(-)
> >>>>
> >>>> diff --git a/drivers/gpu/drm/vkms/vkms_composer.c b/drivers/gpu/drm/vkms/vkms_composer.c
> >>>> index e555bf9c1aee..54fc5161d565 100644
> >>>> --- a/drivers/gpu/drm/vkms/vkms_composer.c
> >>>> +++ b/drivers/gpu/drm/vkms/vkms_composer.c
> >>>> @@ -312,7 +312,7 @@ static void blend(struct vkms_writeback_job *wb,
> >>>> * buffer [1]
> >>>> */
> >>>> current_plane->pixel_read_line(
> >>>> - current_plane->frame_info,
> >>>> + current_plane,
> >>>> x_start,
> >>>> y_start,
> >>>> direction,
> >>>> diff --git a/drivers/gpu/drm/vkms/vkms_drv.h b/drivers/gpu/drm/vkms/vkms_drv.h
> >>>> index ccc5be009f15..a4f6456cb971 100644
> >>>> --- a/drivers/gpu/drm/vkms/vkms_drv.h
> >>>> +++ b/drivers/gpu/drm/vkms/vkms_drv.h
> >>>> @@ -75,6 +75,8 @@ enum pixel_read_direction {
> >>>> READ_RIGHT
> >>>> };
> >>>>
> >>>> +struct vkms_plane_state;
> >>>> +
> >>>> /**
> >>>> <<<<<<< HEAD
> >>>> * typedef pixel_read_line_t - These functions are used to read a pixel line in the source frame,
> >>>> @@ -87,8 +89,8 @@ enum pixel_read_direction {
> >>>> * @out_pixel: Pointer where to write the pixel value. Pixels will be written between x_start and
> >>>> * x_end.
> >>>> */
> >>>> -typedef void (*pixel_read_line_t)(struct vkms_frame_info *frame_info, int x_start, int y_start, enum
> >>>> - pixel_read_direction direction, int count, struct pixel_argb_u16 out_pixel[]);
> >>>> +typedef void (*pixel_read_line_t)(struct vkms_plane_state *frame_info, int x_start, int y_start,
> >>>> + enum pixel_read_direction direction, int count, struct pixel_argb_u16 out_pixel[]);
> >>>
> >>> This is the second or third time in this one series changing this type.
> >>> Could you not do the change once, in its own patch if possible?
> >>
> >> Sorry, this is not a change here, but a wrong formatting (missed when
> >> rebasing).
> >>
> >> Do you think that it make sense to re-order my patches and put this
> >> typedef at the end? This way it is never updated.
I'm not sure, I haven't checked how it would change your patches. The
intermediate changes might get a lot uglier?
Just try to fold changes so that you don't need to change something
twice over the series unless there is a good reason to. "How hard would
it be to review this?" is my measure stick.
> >>
> >>>>
> >>>> /**
> >>>> * vkms_plane_state - Driver specific plane state
> >>>> diff --git a/drivers/gpu/drm/vkms/vkms_formats.c b/drivers/gpu/drm/vkms/vkms_formats.c
> >>>> index 46daea6d3ee9..515c80866a58 100644
> >>>> --- a/drivers/gpu/drm/vkms/vkms_formats.c
> >>>> +++ b/drivers/gpu/drm/vkms/vkms_formats.c
> >>>> @@ -33,7 +33,8 @@ static size_t packed_pixels_offset(const struct vkms_frame_info *frame_info, int
> >>>> */
> >>>> return fb->offsets[plane_index] +
> >>>> (y / drm_format_info_block_width(format, plane_index)) * fb->pitches[plane_index] +
> >>>> - (x / drm_format_info_block_height(format, plane_index)) * format->char_per_block[plane_index];
> >>>> + (x / drm_format_info_block_height(format, plane_index)) *
> >>>> + format->char_per_block[plane_index];
> >>>
> >>> Shouldn't this be in the patch that added this code in the first place?
> >>
> >> Same as above, a wrong formatting, I will remove this change and keep
> >> everything on one line (even if it's more than 100 chars, it is easier to
> >> read).
Personally I agree that readability is more important than strict line
length limits. I'm not sure how the kernel rolls there.
> >>
> >>>> }
> >>>>
> >>>> /**
> >>>> @@ -84,6 +85,32 @@ static int get_step_1x1(struct drm_framebuffer *fb, enum pixel_read_direction di
> >>>> }
> >>>> }
> >>>>
> >>>> +/**
> >>>> + * get_subsampling() - Get the subsampling value on a specific direction
> >>>
> >>> subsampling divisor
> >>
> >> Thanks for this precision.
> >>
> >>>> + */
> >>>> +static int get_subsampling(const struct drm_format_info *format,
> >>>> + enum pixel_read_direction direction)
> >>>> +{
> >>>> + if (direction == READ_LEFT || direction == READ_RIGHT)
> >>>> + return format->hsub;
> >>>> + else if (direction == READ_DOWN || direction == READ_UP)
> >>>> + return format->vsub;
> >>>> + return 1;
> >>>
> >>> In this and the below function, personally I'd prefer switch-case, with
> >>> a cannot-happen-scream after the switch, so the compiler can warn about
> >>> unhandled enum values.
> >>
> >> As for the previous patch, I did not know about this compiler feature,
> >> thanks!
> >>
> >>>> +}
> >>>> +
> >>>> +/**
> >>>> + * get_subsampling_offset() - Get the subsampling offset to use when incrementing the pixel counter
> >>>> + */
> >>>> +static int get_subsampling_offset(const struct drm_format_info *format,
> >>>> + enum pixel_read_direction direction, int x_start, int y_start)
> >>>
> >>> 'start' values as "increments" for a pixel counter? Is something
> >>> misnamed here?
> >>>
> >>> Is it an increment or an offset?
> >>
> >> I don't really know how to name the function. I'm open to suggestions
> >> x_start and y_start are really the coordinate of the starting reading point.
I looks like it's an offset, so "offset" and "start" are good words.
Then the only misleading piece is the doc:
"Get the subsampling offset to use when incrementing the pixel counter"
This sounds like the offset is used when incrementing a counter, that
is, counter is increment by offset each time. That's my problem with
this.
Fix just the doc, and it's good, I think.
> >>
> >> To explain what it does:
> >>
> >> When using subsampling, you have to read the next pixel of planes[1..4]
> >> not at the same "speed" as plane[0]. But I can't only rely on
> >> "read_pixel_count % subsampling == 0", because it means that the pixel
> >> incrementation on planes[1..4] may not be aligned with the buffer (if
> >> hsub=2 and the start pixel is 1, I need to increment planes[1..4] only
> >> for x=2,4,6... not 1,3,5...).
> >>
> >> A way to ensure this is to add an "offset" to count, which ensure that the
> >> count % subsampling == 0 on the correct pixel.
Yes, I think I did get that feeling from the code eventually somehow,
but it wouldn't hurt to explain it in the comment.
"An offset for keeping the chroma siting consistent regardless of
x_start and y_start" maybe?
> >>
> >> I made an error, the switch case must be (as count is always counting up,
> >> for "inverted" reading direction a negative number ensure that
> >> %subsampling == 0 on the correct pixel):
> >>
> >> switch (direction) {
> >> case READ_UP:
> >> return -y_start;
> >> case READ_DOWN:
> >> return y_start;
> >> case READ_LEFT:
> >> return -x_start;
> >> case READ_RIGHT:
> >> return x_start;
> >> }
Yes, the inverted reading directions are different indeed. I did not
think through if this works also for sub-sampling divisors > 2 which I
don't think are ever used.
Does IGT find this mistake? If not, maybe IGT should be extended.
> >>
> >>>> +{
> >>>> + if (direction == READ_RIGHT || direction == READ_LEFT)
> >>>> + return x_start;
> >>>> + else if (direction == READ_DOWN || direction == READ_UP)
> >>>> + return y_start;
> >>>> + return 0;
> >>>> +}
> >>>> +
> >>
> >> [...]
> >>
> >>>> +static void yuv_u8_to_argb_u16(struct pixel_argb_u16 *argb_u16, const struct pixel_yuv_u8 *yuv_u8,
> >>>> + enum drm_color_encoding encoding, enum drm_color_range range)
> >>>> +{
> >>>> + static const s16 bt601_full[3][3] = {
> >>>> + { 256, 0, 359 },
> >>>> + { 256, -88, -183 },
> >>>> + { 256, 454, 0 },
> >>>> + };
> >>
> >> [...]
> >>
> >>>> +
> >>>> + u8 r = 0;
> >>>> + u8 g = 0;
> >>>> + u8 b = 0;
> >>>> + bool full = range == DRM_COLOR_YCBCR_FULL_RANGE;
> >>>> + unsigned int y_offset = full ? 0 : 16;
> >>>> +
> >>>> + switch (encoding) {
> >>>> + case DRM_COLOR_YCBCR_BT601:
> >>>> + ycbcr2rgb(full ? bt601_full : bt601,
> >>>
> >>> Doing all these conditional again pixel by pixel is probably
> >>> inefficient. Just like with the line reading functions, you could pick
> >>> the matrix in advance.
> >>
> >> I don't think the performance impact is huge (it's only a pair of if), but
> >> yes, it's an easy optimization.
> >>
> >> I will create a conversion_matrix structure:
> >>
> >> struct conversion_matrix {
> >> s16 matrix[3][3];
> >> u16 y_offset;
> >> }
When defining such a struct type, it would be good to document the
matrix layout (which one is row, which one is column), and what the s16
mean (fixed point?).
Try to not mix signed and unsigned types, too. The C implicit type
promotion rules can be surprising. Just make everything signed while
computing, and convert to/from unsigned only for storage.
> >>
> >> I will create a `get_conversion_matrix_to_argb_u16` function to get this
> >> structure from a format+encoding+range.
> >>
> >> I will also add a field `conversion_matrix` in struct vkms_plane_state to
> >> get this matrix only once per plane setup.
Alright. Let's see how that works.
> >>
> >>
> >>>> + yuv_u8->y, yuv_u8->u, yuv_u8->v, y_offset, &r, &g, &b);
> >>>> + break;
> >>>> + case DRM_COLOR_YCBCR_BT709:
> >>>> + ycbcr2rgb(full ? rec709_full : rec709,
> >>>> + yuv_u8->y, yuv_u8->u, yuv_u8->v, y_offset, &r, &g, &b);
> >>>> + break;
> >>>> + case DRM_COLOR_YCBCR_BT2020:
> >>>> + ycbcr2rgb(full ? bt2020_full : bt2020,
> >>>> + yuv_u8->y, yuv_u8->u, yuv_u8->v, y_offset, &r, &g, &b);
> >>>> + break;
> >>>> + default:
> >>>> + pr_warn_once("Not supported color encoding\n");
> >>>> + break;
> >>>> + }
> >>>> +
> >>>> + argb_u16->r = r * 257;
> >>>> + argb_u16->g = g * 257;
> >>>> + argb_u16->b = b * 257;
> >>>
> >>> I wonder. Using 8-bit fixed point precision seems quite coarse for
> >>> 8-bit pixel formats, and it's going to be insufficient for higher bit
> >>> depths. Was supporting e.g. 10-bit YUV considered? There is even
> >>> deeper, too, like DRM_FORMAT_P016.
> >>
> >> It's a good point, as I explained above, I took the conversion part as a
> >> "black box" to avoid breaking (and debugging) stuff. I think it's easy to
> >> switch to s32 bits matrix with 16.16 bits (or anything with more than 16 bits in
> >> the float part).
> >>
> >> Maybe Arthur have an opinion on this?
> >
> > Yeah, I too don't see why not we could do that. The 8-bit precision was
> > sufficient for those formats, but as well noted by Pekka this could be a
> > problem for higher bit depths. I just need to make my terrible python
> > script spit those values XD.
>
> Finally, I got it working with 32-bit precision.
>
> I basically threw all my untrusted python code away, and started using
> the colour python framework suggested by Sebastian[1]. After knowing the
> right values (and staring at numbers for hours), I found that with a
> little bit of rounding, the conversion works.
>
> Also, while at it, I changed the name rec709 to bt709 to follow the
> pattern and added "_full" to the full ranges matrices.
>
> While using the library, I noticed that the red component is wrong on
> the color red in one test case.
>
> [1]: https://lore.kernel.org/all/20240115150600.GC160656@toolbox/
That all sounds good. I wish the kernel code contained comments
explaining how exactly you computed those matrices with python/colour.
If the python snippets are not too long, including them verbatim as
code comments would be really nice for both reviewers and posterity.
The same for the VKMS unit tests, too, how you got the expected result
values.
>
> Best Regards,
> ~Arthur Grillo
>
> ---
>
> diff --git a/drivers/gpu/drm/vkms/tests/vkms_format_test.c b/drivers/gpu/drm/vkms/tests/vkms_format_test.c
> index f66584549827..4cee3c2d8d84 100644
> --- a/drivers/gpu/drm/vkms/tests/vkms_format_test.c
> +++ b/drivers/gpu/drm/vkms/tests/vkms_format_test.c
> @@ -59,7 +59,7 @@ static struct yuv_u8_to_argb_u16_case yuv_u8_to_argb_u16_cases[] = {
> {"white", {0xff, 0x80, 0x80}, {0x0000, 0xffff, 0xffff, 0xffff}},
> {"gray", {0x80, 0x80, 0x80}, {0x0000, 0x8000, 0x8000, 0x8000}},
> {"black", {0x00, 0x80, 0x80}, {0x0000, 0x0000, 0x0000, 0x0000}},
> - {"red", {0x35, 0x63, 0xff}, {0x0000, 0xffff, 0x0000, 0x0000}},
> + {"red", {0x36, 0x63, 0xff}, {0x0000, 0xffff, 0x0000, 0x0000}},
> {"green", {0xb6, 0x1e, 0x0c}, {0x0000, 0x0000, 0xffff, 0x0000}},
> {"blue", {0x12, 0xff, 0x74}, {0x0000, 0x0000, 0x0000, 0xffff}},
> },
> diff --git a/drivers/gpu/drm/vkms/vkms_formats.c b/drivers/gpu/drm/vkms/vkms_formats.c
> index e06bbd7c0a67..043f23dbf80d 100644
> --- a/drivers/gpu/drm/vkms/vkms_formats.c
> +++ b/drivers/gpu/drm/vkms/vkms_formats.c
> @@ -121,10 +121,12 @@ static void RGB565_to_argb_u16(u8 **src_pixels, struct pixel_argb_u16 *out_pixel
> out_pixel->b = drm_fixp2int_round(drm_fixp_mul(fp_b, fp_rb_ratio));
> }
>
> -static void ycbcr2rgb(const s16 m[3][3], u8 y, u8 cb, u8 cr, u8 y_offset, u8 *r, u8 *g, u8 *b)
> +#define BIT_DEPTH 32
> +
> +static void ycbcr2rgb(const s64 m[3][3], u8 y, u8 cb, u8 cr, u8 y_offset, u8 *r, u8 *g, u8 *b)
> {
> - s32 y_16, cb_16, cr_16;
> - s32 r_16, g_16, b_16;
> + s64 y_16, cb_16, cr_16;
> + s64 r_16, g_16, b_16;
>
> y_16 = y - y_offset;
> cb_16 = cb - 128;
> @@ -134,9 +136,18 @@ static void ycbcr2rgb(const s16 m[3][3], u8 y, u8 cb, u8 cr, u8 y_offset, u8 *r,
> g_16 = m[1][0] * y_16 + m[1][1] * cb_16 + m[1][2] * cr_16;
> b_16 = m[2][0] * y_16 + m[2][1] * cb_16 + m[2][2] * cr_16;
>
> - *r = clamp(r_16, 0, 0xffff) >> 8;
> - *g = clamp(g_16, 0, 0xffff) >> 8;
> - *b = clamp(b_16, 0, 0xffff) >> 8;
> + // rounding the values
> + r_16 = r_16 + (1LL << (BIT_DEPTH - 4));
> + g_16 = g_16 + (1LL << (BIT_DEPTH - 4));
> + b_16 = b_16 + (1LL << (BIT_DEPTH - 4));
> +
> + r_16 = clamp(r_16, 0, (1LL << (BIT_DEPTH + 8)) - 1);
> + g_16 = clamp(g_16, 0, (1LL << (BIT_DEPTH + 8)) - 1);
> + b_16 = clamp(b_16, 0, (1LL << (BIT_DEPTH + 8)) - 1);
Where do the BIT_DEPTH - 4 and BIT_DEPTH + 8 come from?
> +
> + *r = r_16 >> BIT_DEPTH;
> + *g = g_16 >> BIT_DEPTH;
> + *b = b_16 >> BIT_DEPTH;
> }
...
> >
> >> Just to be sure, the DRM subsystem don't have such matrix somewhere? It
> >> can be nice to avoid duplicating them.
> >
> > As to my knowledge it does not exist on DRM, I think those are normally
> > on the hardware itself (*please* correct me if I'm wrong).
I couldn't find a matrix type either on a quick glance, but there is
drm_fixed.h for a couple different fixed point formats, it seems. FWIW.
drm_fixed.h didn't feel very appealing for this here.
> >
> > But, v4l2 has a similar table on
> > drivers/media/common/v4l2-tpg/v4l2-tpg-core.c (Actually, I started my
> > code based on this), unfortunately it's only 8-bit too.
Thanks,
pq
Attachment:
pgpsxiWmgQ6ub.pgp
Description: OpenPGP digital signature
