From: Robin Gareus <robin@gareus.org>
To: Daniel Mack <daniel@zonque.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, clemens@ladisch.de,
smilingthax@googlemail.com,
David Henningsson <david.henningsson@canonical.com>
Subject: Re: [WIP PATCH] Scarlett mixer interface for 6i6, 18i6, 18i8 and 18i20.
Date: Wed, 08 Oct 2014 23:21:54 +0200 [thread overview]
Message-ID: <5435AAF2.5040909@gareus.org> (raw)
In-Reply-To: <54358AA6.7040205@zonque.org>
Thanks David for picking this up.
On 10/08/2014 09:04 PM, Daniel Mack wrote:
>> +
>> +/* #define WITH_METER */
>> +/* #define WITH_LOGSCALEMETER */
>
> These should either be converted to module parameters, or removed
> alltogether. Why are they configurable, anyway?
Mainly because I lost interest in Focusrite devices before finishing the
work. They were handy during initial development and the idea was to
just enable them by default at some point.
Last I checked they both worked fine for the 18i6, but it seems support
other Scarlett devices is missing and/or untested, so I guess they're
commented out for that reason.
> +#define CTL_SWITCH(cmd, off, no, count, name) \
> + do { \
> + err = add_new_ctl(mixer, &usb_scarlett_ctl_switch, cmd, off, no, 2,
count, name, NULL, &elem); \
> + if (err < 0) \
> + return err; \
> + } while (0)
curious, why "do { } while (0)" and not just "{ }" ?
> Hmm, I don't really like the style of magically returning from macros
Yes, same here. I'm initially responsible for one such macro and wanted
to get rid of it. I'm sorry if that lead Tobias to adding more in that
style.
Cheers!
robin
next prev parent reply other threads:[~2014-10-08 21:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 15:16 [WIP PATCH] Scarlett mixer interface for 6i6, 18i6, 18i8 and 18i20 David Henningsson
2014-10-07 15:24 ` Tobias Hoffmann
2014-10-08 19:04 ` Daniel Mack
2014-10-08 21:21 ` Robin Gareus [this message]
2014-10-08 22:06 ` Tobias Hoffmann
2014-10-09 8:39 ` Takashi Iwai
2014-10-08 22:49 ` Tobias Hoffmann
2014-10-09 8:31 ` Daniel Mack
2014-10-09 10:13 ` Tobias Hoffmann
2014-10-13 13:30 ` David Henningsson
2014-10-09 8:35 ` Takashi Iwai
2014-10-13 10:58 ` Tobias Hoffmann
2014-10-13 11:38 ` Clemens Ladisch
2014-10-13 12:02 ` Tobias Hoffmann
2014-10-13 12:09 ` Clemens Ladisch
2014-10-13 12:21 ` Tobias Hoffmann
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=5435AAF2.5040909@gareus.org \
--to=robin@gareus.org \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=daniel@zonque.org \
--cc=david.henningsson@canonical.com \
--cc=smilingthax@googlemail.com \
--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 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.