From: Clemens Ladisch <clemens@ladisch.de>
To: LCID Fire <lcid-fire@gmx.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: Some questions on snd_kontrol_new
Date: Mon, 10 Nov 2008 09:56:05 +0100 [thread overview]
Message-ID: <4917F725.5040401@ladisch.de> (raw)
In-Reply-To: <49157D12.8060305@gmx.net>
LCID Fire wrote:
> Could someone get me some insight into the snd_kontrol_new?
> I'm especially interested in the "private_value" and "index" field. At
> least in usb_mixer.c it seems to me like private_value is used as the
> index!? If that's the case, when should index be used and when
> private_value?
The index field is used when several controls have the same name.
The private_value field can be used by drivers for any purpose.
The functions for the Audigy 2 NX's LEDs store the LED number in the
private_value field so that the same function can be used for all three
LEDs without having to look at the control name.
> Is there any special convention for the string of "name" field?
linux/Documentation/sound/alsa/ControlNames.txt
HTH
Clemens
prev parent reply other threads:[~2008-11-10 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 11:36 [PATCH] ALSA: HDSP: check for io box before uploading firmware Tim Blechmann
2008-11-08 11:50 ` Some questions on snd_kontrol_new LCID Fire
2008-11-10 8:56 ` Clemens Ladisch [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=4917F725.5040401@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=lcid-fire@gmx.net \
/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