All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: linux-media <linux-media@vger.kernel.org>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [Q] Why is it needed to add an alsa module to v4l audio capture devices?
Date: Mon, 11 Jun 2012 10:05:20 +0200	[thread overview]
Message-ID: <2041118.ct8h3d9SmG@avalon> (raw)
In-Reply-To: <CALF0-+VmR6izw6zXj+kOsrQDPN94v8jqhoRmeYp1vvexuoFJ1Q@mail.gmail.com>

Hi Ezequiel,

On Thursday 07 June 2012 15:26:04 Ezequiel Garcia wrote:
> Hi all,
> 
> (I hope this is a genuine question, and I'm not avoiding my own homework
> here.)
> 
> I'm trying to support the audio part of the stk1160 usb bridge (similar to
> em28xx). Currently, the snd-usb-audio module is being loaded when I
> physically plug my device, but I can't seem to capture any sound with vlc.
> 
> I still have to research and work a lot to understand the connection between
> my device and alsa, and altough I could write a working module similar to
> em28xx-alsa.ko, I still can't figure out why do I need to write one in the
> first place.
> 
> Why is this module suffficient for gspca microphone devices (gspca, to name
> one) and why is a new alsa driver needed for em28xx (or stk1160)?

Some devices expose audio functionality by implementing the UAC (USB Audio 
Class) specification. The snd-usb-audio module is all you should need for 
those devices.

Other vendors support audio by using their own proprietary protocol. In those 
cases you will need a device-specific kernel module.

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2012-06-11  8:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07 18:26 [Q] Why is it needed to add an alsa module to v4l audio capture devices? Ezequiel Garcia
2012-06-11  8:05 ` Laurent Pinchart [this message]
2012-06-11 13:30 ` Mauro Carvalho Chehab
2012-06-11 16:39   ` Ezequiel Garcia

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=2041118.ct8h3d9SmG@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=elezegarcia@gmail.com \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.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.