From: Felix Homann <linuxaudio@showlabor.de>
To: Daniel Mack <zonque@gmail.com>
Cc: alsa-devel@alsa-project.org, Grant Diffey <gdiffey@gmail.com>
Subject: Re: A plea for help on mixer support for Fast Track Ultra (8R)
Date: Wed, 18 May 2011 20:46:20 +0200 [thread overview]
Message-ID: <4DD413FC.2090808@showlabor.de> (raw)
In-Reply-To: <BANLkTinCn2Q+asKhGAoq+3S+AtqyHrg2wg@mail.gmail.com>
Hi Daniel,
Am 18.05.2011 19:51, schrieb Daniel Mack:
>
> Hmm, I'm not sure whether I understand what you're trying to do. You
> want to add mixers that are not added by the generic driver?
I'm adding a mixer to a device that doesn't even tell the driver that a
mixer is present. There's no descriptor for it whatsoever. Nevertheless,
you can control the mixer just like a standard usb audio mixer.
Therefore I wanted to reuse as much of already present code as possible.
Most of all I didn't want to construct any URBs or write new control_get
or _put functions.
The problem is not how to get the mixer for the Fast Track Ultra (FTU)
working. The problem is how to do it without breaking other mixers ;-)
The main problem at the moment is that snd_usb_create_mixer() will not
be called on quirked devices! Take a look at card.c:
snd_usb_create_mixer() will only be called if snd_usb_create_quirk()
returns > 0. But why should we assume that quirked devices don't have
any mixers?
I have forced calling snd_usb_create_mixer() for every device in my
patch set. But this way controls from other devices will show up
multiple times. We definetely don't want that.
If snd_usb_create_mixer() will be called for the FTU then the rest of my
patch set works just fine. So how can I tell card.c to call it? I think
a generic solution would be best, like some entry in quirks-table.h.
> As a general rule, let the check-patch.pl script that ships with the
> kernel have a look at your patches, it will point out obvious coding
> style issues and the like :)
I knew it wasn't ready for submission. After generating the patch I send
I had already corrected the whitespaces and those lines with over 80
characters that weren't just copies from other locations. The remaining
issues like "! cval" and "ERROR: do not use assignment in if condition"
were all taken literally from other locations inside the respective
files. So, besides one C99 comment it's very much in style with the
files I've been working on ;-)
Regards,
Felix
next prev parent reply other threads:[~2011-05-18 18:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-18 15:19 A plea for help on mixer support for Fast Track Ultra (8R) Felix Homann
2011-05-18 15:29 ` Felix Homann
2011-05-18 17:51 ` Daniel Mack
2011-05-18 18:46 ` Felix Homann [this message]
2011-05-18 21:30 ` Daniel Mack
2011-05-19 0:51 ` Grant Diffey
2011-05-19 5:42 ` Takashi Iwai
2011-05-19 6:45 ` Felix Homann
2011-05-19 7:15 ` Clemens Ladisch
2011-05-19 7:24 ` Takashi Iwai
2011-05-19 8:14 ` Felix Homann
2011-05-19 8:52 ` Daniel Mack
2011-05-19 10:56 ` Felix Homann
2011-05-19 11:05 ` Daniel Mack
2011-05-19 12:23 ` Felix Homann
2011-05-19 13:36 ` Felix Homann
2011-05-19 13:42 ` Felix Homann
2011-05-19 14:12 ` Daniel Mack
2011-05-20 10:12 ` Felix Homann
2011-05-20 11:12 ` Daniel Mack
2011-05-20 11:14 ` Felix Homann
2011-05-20 11:37 ` Daniel Mack
2011-05-20 15:08 ` Grant Diffey
2011-05-20 15:43 ` Grant Diffey
2011-05-20 15:52 ` Felix Homann
2011-05-20 15:54 ` Daniel Mack
2011-05-20 16:25 ` Grant Diffey
2011-05-20 16:38 ` Daniel Mack
2011-05-20 16:44 ` Felix Homann
2011-05-20 16:52 ` Felix Homann
2011-05-24 10:11 ` Felix Homann
2011-05-24 10:47 ` Daniel Mack
2011-05-24 11:54 ` Takashi Iwai
2011-05-24 23:55 ` Grant Diffey
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=4DD413FC.2090808@showlabor.de \
--to=linuxaudio@showlabor.de \
--cc=alsa-devel@alsa-project.org \
--cc=gdiffey@gmail.com \
--cc=zonque@gmail.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.