All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org, Sakari Ailus <sakari.ailus@iki.fi>,
	Jacopo Mondi <jacopo@jmondi.org>,
	Xavier Roumegue <xavier.roumegue@oss.nxp.com>,
	linux-imx@nxp.com, kernel@pengutronix.de
Subject: Re: [PATCH 3/7] media: vivid: Add support for the new YUVA and YUVX formats
Date: Thu, 30 Jun 2022 03:17:18 +0300	[thread overview]
Message-ID: <Yrzrjp1wBaPPsXob@pendragon.ideasonboard.com> (raw)
In-Reply-To: <c0568b04-7474-c30f-54ed-20109d8c3730@xs4all.nl>

Hi Hans,

On Wed, Jun 29, 2022 at 03:54:43PM +0200, Hans Verkuil wrote:
> On 16/06/2022 20:36, Laurent Pinchart wrote:
> > Extend vivid to support the newly added YUVA and YUVX pixel formats
> > through the TPG.
> > 
> > Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> 
> Note that v4l-utils should receive a patch adding support for these two
> new formats, esp. since the tpg and vivid uses them.
> 
> Basically just grep for V4L2_PIX_FMT_VUYX/A32 and add support for these
> two new formats.

This requires syncing with the kernel headers. What's the procedure
there, should I wait until the kernel patches get merged in a released
kernel first ?

> > ---
> >  .../media/test-drivers/vivid/vivid-vid-common.c   | 15 +++++++++++++++
> >  1 file changed, 15 insertions(+)
> > 
> > diff --git a/drivers/media/test-drivers/vivid/vivid-vid-common.c b/drivers/media/test-drivers/vivid/vivid-vid-common.c
> > index 19701fe72030..38d788b5cf19 100644
> > --- a/drivers/media/test-drivers/vivid/vivid-vid-common.c
> > +++ b/drivers/media/test-drivers/vivid/vivid-vid-common.c
> > @@ -198,6 +198,21 @@ struct vivid_fmt vivid_formats[] = {
> >  		.planes   = 1,
> >  		.buffers = 1,
> >  	},
> > +	{
> > +		.fourcc   = V4L2_PIX_FMT_YUVA32,
> > +		.vdownsampling = { 1 },
> > +		.bit_depth = { 32 },
> > +		.planes   = 1,
> > +		.buffers = 1,
> > +		.alpha_mask = 0xff000000,
> > +	},
> > +	{
> > +		.fourcc   = V4L2_PIX_FMT_YUVX32,
> > +		.vdownsampling = { 1 },
> > +		.bit_depth = { 32 },
> > +		.planes   = 1,
> > +		.buffers = 1,
> > +	},
> >  	{
> >  		.fourcc   = V4L2_PIX_FMT_GREY,
> >  		.vdownsampling = { 1 },

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2022-06-30  0:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 18:36 [PATCH 0/7] media: nxp: i.MX8 ISI driver Laurent Pinchart
2022-06-16 18:36 ` [PATCH 1/7] media: v4l: Add packed YUV 4:4:4 YUVA and YUVX pixel formats Laurent Pinchart
2022-06-29 13:46   ` Hans Verkuil
2022-06-16 18:36 ` [PATCH 2/7] media: v4l2-tpg: Add support for the new YUVA and YUVX formats Laurent Pinchart
2022-06-28 10:22   ` Jacopo Mondi
2022-06-29 13:47   ` Hans Verkuil
2022-06-16 18:36 ` [PATCH 3/7] media: vivid: " Laurent Pinchart
2022-06-27 23:53   ` Laurent Pinchart
2022-06-28 10:28   ` Jacopo Mondi
2022-06-29 13:47   ` Hans Verkuil
2022-06-29 13:54   ` Hans Verkuil
2022-06-30  0:17     ` Laurent Pinchart [this message]
2022-06-16 18:36 ` [PATCH 4/7] media: v4l2: Make colorspace validity checks more future-proof Laurent Pinchart
2022-06-29 13:50   ` Hans Verkuil
2022-06-30  9:46     ` Sakari Ailus
2022-06-30  9:48       ` Laurent Pinchart
2022-06-30  9:56         ` Hans Verkuil
2022-06-16 18:36 ` [PATCH 5/7] media: v4l2: Sanitize colorspace values in the framework Laurent Pinchart
2022-06-29 13:59   ` Hans Verkuil
2022-06-16 18:36 ` [PATCH 6/7] dt-bindings: media: Add i.MX8 ISI DT bindings Laurent Pinchart
2022-06-17  2:47   ` Rob Herring
2022-06-16 18:36 ` [PATCH 7/7] media: nxp: Add i.MX8 ISI driver Laurent Pinchart
2022-06-17  2:40   ` kernel test robot

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=Yrzrjp1wBaPPsXob@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jacopo@jmondi.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-imx@nxp.com \
    --cc=linux-media@vger.kernel.org \
    --cc=sakari.ailus@iki.fi \
    --cc=xavier.roumegue@oss.nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.