From: Clemens Ladisch <clemens@ladisch.de>
To: "Sebastian H." <vand2@gmx.de>
Cc: Takashi Iwai <tiwai@suse.de>,
Eliot Blennerhassett <eblennerhassett@audioscience.com>,
alsa-devel@alsa-project.org
Subject: Re: asihpi: Control naming
Date: Fri, 01 Oct 2010 15:19:56 +0200 [thread overview]
Message-ID: <4CA5DFFC.40004@ladisch.de> (raw)
In-Reply-To: <4CA5C69B.4000703@gmx.de>
Sebastian H. wrote:
> Am 01.10.2010 09:05, schrieb Clemens Ladisch:
> > Those are elements where the simple mixer code doesn't know the
> > direction (because the driver author didn't put "Playback" or "Capture"
> > into the name).
>
> Ok, but I wonder how to interpret this state in which both functions
> return zero.
There are cases where the playback/capture direction is obvious from the
name ("just implement an AI!"), but these can be considered bugs.
In the other cases, the control really doesn't belong to a direction.
(Which doesn't prevent many mixers that have two pages from just
throwing them in with the playback controls.)
Regards,
Clemens
next prev parent reply other threads:[~2010-10-01 13:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 3:44 asihpi: Control naming Eliot Blennerhassett
2010-09-30 5:46 ` Takashi Iwai
2010-09-30 20:23 ` Eliot Blennerhassett
2010-09-30 20:56 ` Takashi Iwai
2010-09-30 21:28 ` Sebastian H.
2010-10-01 7:05 ` Clemens Ladisch
2010-10-01 11:31 ` Sebastian H.
2010-10-01 12:45 ` Raymond Yau
2010-10-01 13:19 ` Clemens Ladisch [this message]
2010-10-01 20:06 ` Sebastian H.
2010-10-02 4:10 ` Raymond Yau
2010-10-02 11:10 ` Sebastian H.
2010-09-30 23:47 ` Mark Brown
2010-10-05 5:10 ` Eliot Blennerhassett
2010-10-05 7:07 ` Clemens Ladisch
2010-10-05 8:14 ` Eliot Blennerhassett
2010-10-05 8:15 ` Eliot Blennerhassett
2010-10-05 9:47 ` Clemens Ladisch
2010-10-05 9:53 ` Takashi Iwai
2010-10-06 22:55 ` asihpi: Control naming, Irritated Currant edition Eliot Blennerhassett
2010-09-30 20:56 ` asihpi: Control naming Takashi Iwai
2010-09-30 6:28 ` David Henningsson
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=4CA5DFFC.40004@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=eblennerhassett@audioscience.com \
--cc=tiwai@suse.de \
--cc=vand2@gmx.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.