mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nas Chung <nas.chung@chipsnmedia.com>
To: Michael Tretter <m.tretter@pengutronix.de>
Cc: "mchehab@kernel.org" <mchehab@kernel.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Sebastian Fricke <sebastian.fricke@collabora.com>
Subject: RE: [PATCH] media: uapi: v4l: Change V4L2_TYPE_IS_CAPTURE condition
Date: Thu, 23 May 2024 01:48:34 +0000	[thread overview]
Message-ID: <SL2P216MB12467C08314BA4B314A8EED6FBF42@SL2P216MB1246.KORP216.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <Zk2kunIzL0ylxHiH@pengutronix.de>

Hi, Michael.

Thank you for the feedback.

>-----Original Message-----
>From: Michael Tretter <m.tretter@pengutronix.de>
>Sent: Wednesday, May 22, 2024 4:55 PM
>To: Nas Chung <nas.chung@chipsnmedia.com>
>Cc: mchehab@kernel.org; linux-media@vger.kernel.org; linux-
>kernel@vger.kernel.org; Sebastian Fricke <sebastian.fricke@collabora.com>
>Subject: Re: [PATCH] media: uapi: v4l: Change V4L2_TYPE_IS_CAPTURE
>condition
>
>On Fri, 17 May 2024 18:49:40 +0900, Nas Chung wrote:
>> We expect V4L2_TYPE_IS_CAPTURE() macro allow only CAPTURE type.
>> But, Inverting OUTPUT type can allow undefined v4l2_buf_type.
>> Check CAPTURE type directly instead of inverting OUTPUT type.
>>
>> Signed-off-by: Nas Chung <nas.chung@chipsnmedia.com>
>> ---
>>  include/uapi/linux/videodev2.h | 8 +++++++-
>>  1 file changed, 7 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/uapi/linux/videodev2.h
>b/include/uapi/linux/videodev2.h
>> index fe6b67e83751..32b10e2b7695 100644
>> --- a/include/uapi/linux/videodev2.h
>> +++ b/include/uapi/linux/videodev2.h
>> @@ -171,7 +171,13 @@ enum v4l2_buf_type {
>>  	 || (type) == V4L2_BUF_TYPE_SDR_OUTPUT			\
>>  	 || (type) == V4L2_BUF_TYPE_META_OUTPUT)
>>
>> -#define V4L2_TYPE_IS_CAPTURE(type) (!V4L2_TYPE_IS_OUTPUT(type))
>> +#define V4L2_TYPE_IS_CAPTURE(type)				\
>> +	((type) == V4L2_BUF_TYPE_VIDEO_CAPTURE			\
>> +	 || (type) == V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE	\
>> +	 || (type) == V4L2_BUF_TYPE_VBI_CAPTURE			\
>> +	 || (type) == V4L2_BUF_TYPE_SLICED_VBI_CAPTURE		\
>> +	 || (type) == V4L2_BUF_TYPE_SDR_CAPTURE			\
>> +	 || (type) == V4L2_BUF_TYPE_META_CAPTURE)
>
>Maybe adding a V4L2_TYPE_IS_VALID(type) macro would be helpful to define
>TYPE_IS_CAPTURE as all valid types that are not OUTPUT:
>
>	#define V4L2_TYPE_IS_VALID(type) \
>		((type) >= V4L2_BUF_TYPE_VIDEO_CAPTURE \
>		&& (type) <= V4L2_BUF_TYPE_META_OUTPUT)
>
>	#define V4L2_TYPE_IS_CAPTURE(type) \
>		(V4L2_TYPE_IS_VALID(type) && !V4L2_TYPE_IS_OUTPUT(type))
>
>This would avoid keeping the two explicit lists of OUTPUT and CAPTURE
>types.

I agree that it's better to add a V4L2_TYPE_IS_VALID(type) macro.
I will address this in V2.

Thanks.
Nas.

>
>Michael
>
>>
>>  enum v4l2_tuner_type {
>>  	V4L2_TUNER_RADIO	     = 1,
>> --
>> 2.25.1
>>
>>
>>

      reply	other threads:[~2024-05-23  1:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17  9:49 Nas Chung
2024-05-17 10:10 ` Sebastian Fricke
2024-05-17 12:33   ` Nas Chung
2024-05-22  7:54 ` Michael Tretter
2024-05-23  1:48   ` Nas Chung [this message]

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=SL2P216MB12467C08314BA4B314A8EED6FBF42@SL2P216MB1246.KORP216.PROD.OUTLOOK.COM \
    --to=nas.chung@chipsnmedia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=m.tretter@pengutronix.de \
    --cc=mchehab@kernel.org \
    --cc=sebastian.fricke@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®