All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: clemens@ladish.de, alsa-devel@alsa-project.org,
	940145@bugs.launchpad.net
Subject: Re: [PATCH] USB-Audio: Disable "Logitech USB Headset" iec958 device
Date: Thu, 08 Mar 2012 16:47:31 +0100	[thread overview]
Message-ID: <4F58D493.6050703@ladisch.de> (raw)
In-Reply-To: <1331115784-3541-1-git-send-email-david.henningsson@canonical.com>

David Henningsson wrote:
> Because Logitech USB Headsets do not have any digital devices,
> prevent them from being opened. This simplifies probing the
> device in PulseAudio.
>
> --- a/src/conf/cards/USB-Audio.conf
> +++ b/src/conf/cards/USB-Audio.conf
> @@ -36,6 +36,8 @@ USB-Audio.pcm.surround40_type {
>  # number for the iec958 device can be changed here.
>  USB-Audio.pcm.iec958_device {
>  	# "NoiseBlaster 3000" 42
> +	# Make sure we can't open this device digitally, because it does not exist
> +	"Logitech USB Headset" 999
>  }

This introduces a blacklist of devices that do not have digital outputs.
There are lot of other such devices that need such entries to make PA
work better, but at the moment, the only alternative would be a whitelist
of devices with digital outputs, which would have exactly the same
maintenance problems.

As long as there is no mechanism for .conf files to find out whether
a USB device actually has digital outputs, there's no better way to
solve the problem.


Regards,
Clemens

      parent reply	other threads:[~2012-03-08 15:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07 10:23 [PATCH] USB-Audio: Disable "Logitech USB Headset" iec958 device David Henningsson
2012-03-08  0:57 ` Raymond Yau
2012-03-08  5:35   ` David Henningsson
2012-03-08 15:06     ` Takashi Iwai
2012-03-08 15:47 ` Clemens Ladisch [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=4F58D493.6050703@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=940145@bugs.launchpad.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladish.de \
    --cc=david.henningsson@canonical.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.