linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: claus.stovgaard@gmail.com
To: linux-media@vger.kernel.org
Subject: VIDIOC_QUERYCAP on v4l subdevice - v4l-subdev*
Date: Tue, 01 Nov 2022 13:50:16 +0100	[thread overview]
Message-ID: <93834b3d7d4abfabdc7285af0c5e57d015c97107.camel@gmail.com> (raw)

Hi Folks.

I am working on a system based around the Intel Apollo Lake with an
IPU4. The system is having a configuration with a number of subdevices.
Going from v4l-subdev0 to v4-subdev10.

Running gst-device-monitor-1.0 results in a number of errors like.

GStreamer-CRITICAL **: 13:27:36.763:
gst_element_message_full_with_details: assertion 'GST_IS_ELEMENT
(element)' failed        

The reason is because a VIDIOC_QUERYCAP on the subdevice fails.

Looking at the documentation

https://www.kernel.org/doc/html/latest/userspace-api/media/v4l/vidioc-querycap.html

it states that "All V4L2 devices support the VIDIOC_QUERYCAP ioctl"

On the other hand VIDIOC_QUERYCAP is not part of the subset mentioned
in documentation for V4L2 sub-device.

https://www.kernel.org/doc/html/latest/driver-api/media/v4l2-subdev.html

So is I correct that gstreamer has a bug in gst-device-monitor-1.0, and
it should not try to use the VIDIOC_QUERYCAP ioctl for a sub-device?

It could be that gstreamer should just skip the sub-device.

Regards
Claus Stovgaard


             reply	other threads:[~2022-11-01 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 12:50 claus.stovgaard [this message]
2022-11-02  8:15 ` VIDIOC_QUERYCAP on v4l subdevice - v4l-subdev* Jacopo Mondi

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=93834b3d7d4abfabdc7285af0c5e57d015c97107.camel@gmail.com \
    --to=claus.stovgaard@gmail.com \
    --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).