From: Jassi Brar <jaswinder.singh@linaro.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Mark Hills <mark@pogo.org.uk>
Subject: Re: [PATCH 1/2] snd-usb-audio: Skip un-parseable mixer units instead of erroring
Date: Mon, 16 Apr 2012 12:00:31 +0530 [thread overview]
Message-ID: <CAJe_ZhcDBunFuHOzrzHHiMyNkLnvoCTZm8NifDSWGnRN-fqM2Q@mail.gmail.com> (raw)
In-Reply-To: <s5hk41ip15p.wl%tiwai@suse.de>
On 15 April 2012 00:54, Takashi Iwai <tiwai@suse.de> wrote:
> At Sat, 14 Apr 2012 17:19:23 +0100,
> Mark Hills wrote:
>>
>> Some interfaces reference endpoints which do not exists. To
>> accomodate these, do not fail completely, but skip over them.
>>
>> This allows the Electrix Ebox-44 with earlier firmware to be
>> detected and used for audio.
>
> Does the driver warn something? Ignoring silently doesn't sound
> right...
>
I had been looking into UAC2 device side driver. Debugging
it, enlightened me of the mess the USB audio implementations are in.
IMHO ALSA support usb audio better than AppleUSBAudio ... guess they
are too embarrassed of the code that they no longer keep it public :D
Of course, major blame is on buggy implementation/reporting of configuration
by the devices.
I was wondering if it would make sense for ALSA to first 'mend' any
discrepancies in the reported configuration (say by having optional
callbacks registered against vid/pid), and then instantiate the sound card
which only refers to the cached sanitized configuration ?
That way, we could write usb-audio core to UAC specification, while
keeping vendor specific hacks out separately. Or so do I think.
Regards.
-Jassi
prev parent reply other threads:[~2012-04-16 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 16:19 [PATCH 1/2] snd-usb-audio: Skip un-parseable mixer units instead of erroring Mark Hills
2012-04-14 16:19 ` [PATCH 2/2] snd-usb-audio: Replace mixer for Electrix Ebox-44 Mark Hills
2012-04-14 19:24 ` [PATCH 1/2] snd-usb-audio: Skip un-parseable mixer units instead of erroring Takashi Iwai
2012-04-14 20:38 ` Mark Hills
2012-04-15 13:41 ` Takashi Iwai
2012-04-16 6:30 ` Jassi Brar [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=CAJe_ZhcDBunFuHOzrzHHiMyNkLnvoCTZm8NifDSWGnRN-fqM2Q@mail.gmail.com \
--to=jaswinder.singh@linaro.org \
--cc=alsa-devel@alsa-project.org \
--cc=mark@pogo.org.uk \
--cc=tiwai@suse.de \
/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).