public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: "Bård Eirik Winther" <bwinther@cisco.com>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: UVC and V4L2_CAP_AUDIO
Date: Thu, 25 Jul 2013 11:10:15 +0200	[thread overview]
Message-ID: <1530000.NI5gtVtkJY@avalon> (raw)
In-Reply-To: <201307251103.13456.hverkuil@xs4all.nl>

Hi Hans,

On Thursday 25 July 2013 11:03:13 Hans Verkuil wrote:
> Hi Laurent,
> 
> While working on adding alsa streaming support to qv4l2 we noticed that uvc
> doesn't set this capability telling userspace that the webcam supports
> audio.
> 
> Is it possible at all in the uvc driver to determine whether or not a uvc
> webcam has a microphone?

Not without dirty hacks. The UVC interfaces don't report whether the device 
has an audio function, the driver would need to look at all the interfaces of 
the parent USB device and find out whether they match one of the USB audio 
drivers. That's not something I would be inclined to merge in the uvcvideo 
driver.

> If not, then it looks like the only way to find the associated alsa device
> is to use libmedia_dev (or its replacement, although I wonder if anyone is
> still working on that).

I need to post the code I have. I'll try to do that next week.

> And in particular, the presence of CAP_AUDIO cannot be used to determine
> whether the device has audio capabilities, it can only be used to determine
> if the V4L2 audio ioctls are supported. That would have to be clarified in
> the spec.

The V4L2 audio ioctls are definitely not supported by the uvcvideo driver :-)

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-07-25  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25  9:03 UVC and V4L2_CAP_AUDIO Hans Verkuil
2013-07-25  9:10 ` Laurent Pinchart [this message]
2013-07-25 13:11   ` Devin Heitmueller
2013-07-25 13:19     ` Laurent Pinchart

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=1530000.NI5gtVtkJY@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=bwinther@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --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