From: Johannes Berg <johannes@sipsolutions.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Dmitry Torokhov <dtor@insightbb.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Richard Purdie <rpurdie@rpsys.net>,
linux-input <linux-input@atrey.karlin.mff.cuni.cz>,
alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] sound connector detection
Date: Tue, 04 Jul 2006 20:51:55 +0200 [thread overview]
Message-ID: <1152039115.1834.1.camel@localhost> (raw)
In-Reply-To: <s5hmzbp2wlu.wl%tiwai@suse.de>
[-- Attachment #1: Type: text/plain, Size: 767 bytes --]
On Tue, 2006-07-04 at 17:55 +0200, Takashi Iwai wrote:
> Such a control element doesn't have to be IFACE_MIXER if you want to
> hide. You can use IFACE_CARD, for example, for a card-specific
> element but not belonging to the mixer component.
Oh. Good, I'll submit a patch to change that then so that it isn't
there. Someone's probably gonna lart me for it though because it isn't
visible any more ;)
> That's true. OTOH, invoking a command at each time isn't always a
> good solution, depending on the event-frequency and heaviness.
Yeah, that's the downside of a hotplug type approach.
Well, I'm open for other suggestions. I just dislike the current state
of pushing events through the alsa control elements. Sorta feels wrong.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2006-07-04 18:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 12:49 sound connector detection Johannes Berg
2006-07-01 20:09 ` Dmitry Torokhov
2006-07-02 9:28 ` Richard Purdie
2006-07-03 2:48 ` Dmitry Torokhov
2006-07-03 13:31 ` Johannes Berg
2006-07-03 13:30 ` Johannes Berg
2006-07-04 15:55 ` [Alsa-devel] " Takashi Iwai
2006-07-04 18:51 ` Johannes Berg [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=1152039115.1834.1.camel@localhost \
--to=johannes@sipsolutions.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=dtor@insightbb.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rpurdie@rpsys.net \
--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).