linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: linux-media@vger.kernel.org, linux-input@vger.kernel.org,
	 Erling Ljunggren <hljunggr@cisco.com>
Subject: Re: [PATCH 1/6] media: videodev2.h: add V4L2_CAP_EDID
Date: Thu, 29 Aug 2024 09:25:42 +0200	[thread overview]
Message-ID: <CAPybu_1DG9be7fKBiLYtrPfYayeFYmw2nAeoRb7rjA+oHduuHg@mail.gmail.com> (raw)
In-Reply-To: <d78f8808-2583-4a73-952a-8dfdcdf9b6e0@xs4all.nl>

On Thu, Aug 29, 2024 at 9:11 AM Hans Verkuil <hverkuil-cisco@xs4all.nl> wrote:
>
> On 28/08/2024 14:51, Ricardo Ribalda Delgado wrote:
> > Hi Hans
> >
> > On Fri, Aug 9, 2024 at 10:14 AM Hans Verkuil <hverkuil-cisco@xs4all.nl> wrote:
> >>
> >> From: Erling Ljunggren <hljunggr@cisco.com>
> >>
> >> Add capability flag to indicate that the device is an EDID-only device.
> >>
> >> Signed-off-by: Erling Ljunggren <hljunggr@cisco.com>
> >> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
> >> ---
> >>  include/uapi/linux/videodev2.h | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/include/uapi/linux/videodev2.h b/include/uapi/linux/videodev2.h
> >> index 4e91362da6da..987c821aed79 100644
> >> --- a/include/uapi/linux/videodev2.h
> >> +++ b/include/uapi/linux/videodev2.h
> >> @@ -502,6 +502,7 @@ struct v4l2_capability {
> >>  #define V4L2_CAP_META_CAPTURE          0x00800000  /* Is a metadata capture device */
> >>
> >>  #define V4L2_CAP_READWRITE              0x01000000  /* read/write systemcalls */
> >> +#define V4L2_CAP_EDID                  0x02000000  /* Is an EDID-only device */
> >
> > Would it make sense to add a check for "EDID-only", I mean, if the
> > driver sets this cap, then it should not set V4L2_CAP_STREAMING or others.
> >
> > The test could be in the core or even in v4l2-compliance.
>
> Good point. It is easy to add this to v4l2-compliance.
>
> I noticed that the v4l2 core doesn't check for invalid caps combinations. It is
> left to v4l2-compliance to check that. So I think I'll keep the check there.

cool! Thanks

Reviewed-by: Ricardo Ribalda <ribalda@chromium.org>


>
> Regards,
>
>         Hans
>
> >
> > Regards!
> >
> >
> >>  #define V4L2_CAP_STREAMING              0x04000000  /* streaming I/O ioctls */
> >>  #define V4L2_CAP_META_OUTPUT           0x08000000  /* Is a metadata output device */
> >>
> >> --
> >> 2.43.0
> >>
> >>
> >
> >
> > --
> > Ricardo Ribalda
> >
>


-- 
Ricardo Ribalda

  reply	other threads:[~2024-08-29  7:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-09  7:57 [PATCH 0/6] media: cec: add support for the Extron DA HD 4K Plus HDMI Splitter Hans Verkuil
2024-08-09  7:57 ` [PATCH 1/6] media: videodev2.h: add V4L2_CAP_EDID Hans Verkuil
2024-08-28 12:37   ` Sebastian Fricke
2024-08-28 12:51   ` Ricardo Ribalda Delgado
2024-08-29  7:11     ` Hans Verkuil
2024-08-29  7:25       ` Ricardo Ribalda Delgado [this message]
2024-08-09  7:57 ` [PATCH 2/6] media: v4l2-dev: handle V4L2_CAP_EDID Hans Verkuil
2024-08-28 12:38   ` Sebastian Fricke
2024-08-29  7:27     ` Ricardo Ribalda Delgado
2024-08-09  7:57 ` [PATCH 3/6] media: docs: Add V4L2_CAP_EDID Hans Verkuil
2024-08-28 12:38   ` Sebastian Fricke
2024-08-29  7:27     ` Ricardo Ribalda Delgado
2024-08-09  7:57 ` [PATCH 4/6] input: serio.h: add SERIO_EXTRON_DA_HD_PLUS Hans Verkuil
2024-08-28 11:25   ` Hans Verkuil
2024-08-28 16:13     ` Dmitry Torokhov
2024-08-28 16:11   ` Dmitry Torokhov
2024-08-09  7:57 ` [PATCH 5/6] media: cec: move cec_get/put_device to header Hans Verkuil
2024-08-09  7:57 ` [PATCH 6/6] media: cec: extron-da-hd-4k-plus: add the Extron DA HD 4K Plus CEC driver Hans Verkuil

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=CAPybu_1DG9be7fKBiLYtrPfYayeFYmw2nAeoRb7rjA+oHduuHg@mail.gmail.com \
    --to=ricardo.ribalda@gmail.com \
    --cc=hljunggr@cisco.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).