media: ti-vpe: vpe: fix v4l2_compliance issue related to xfer_func

All 4 of the "colorspace" components were not originally handled.
Causing issue related to xfer_func not being initialized properly.

This was found with v4l2-compliance test.

Signed-off-by: Benoit Parrot <bparrot@ti.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>

diff --git a/drivers/media/platform/ti-vpe/vpe.c b/drivers/media/platform/ti-vpe/vpe.c
index 23ba6232d7398a49a6430b8d64f41b81d49d0a30..a50511f1e1c37b58666abdc2d32e460a2659d67d 100644 (file)
--- a/drivers/media/platform/ti-vpe/vpe.c
+++ b/drivers/media/platform/ti-vpe/vpe.c
@@ -1582,11 +1582,14 @@ static int vpe_g_fmt(struct file *file, void *priv, struct v4l2_format *f)
                struct vpe_q_data *s_q_data;
                struct v4l2_pix_format_mplane *spix;
 
-               /* get colorspace from the source queue */
+               /* get colorimetry from the source queue */
                s_q_data = get_q_data(ctx, V4L2_BUF_TYPE_VIDEO_OUTPUT_MPLANE);
                spix = &s_q_data->format.fmt.pix_mp;
 
                pix->colorspace = spix->colorspace;
+               pix->xfer_func = spix->xfer_func;
+               pix->ycbcr_enc = spix->ycbcr_enc;
+               pix->quantization = spix->quantization;
        }
 
        return 0;