All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Clemens Ladisch <clemens@ladisch.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Some questions about userspace control elements
Date: Sun, 08 Feb 2015 19:57:25 +0900	[thread overview]
Message-ID: <54D74115.4070202@sakamocchi.jp> (raw)
In-Reply-To: <54D6331A.5070200@ladisch.de>

On Feb 8 2014 00:45, Clemens Ladisch wrote:
> Takashi Sakamoto wrote:
>> On Feb 6 2015 18:38, Clemens Ladisch wrote:
>>> The owner field is used because there is no other field to set the
>>> count.
>>
>> No. In SNDRV_CTL_IOCTL_ELEM_ADD ioctl, struct snd_ctl_elem_info.count
>> has the number of elements in this control, there it's an abuse of
>> member unrelated to the count.
> 
> That is a different count.
> 
> struct snd_ctl_elem_info.count allows a control to have multiple values.
> For example, a stereo volume control has two values.
> 
> kctl.count creates multiple controls.

Oh, I confused these two 'count's... I'm OK that the count member in
struct snd_kcontrol means the number of controls (elements) with the
same type, and the count member in struct snd_ctl_elem_info means the
number of values in a controls, then the event occurs every controls,
not for values.


Thanks

Takashi Sakamoto

      reply	other threads:[~2015-02-08 10:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 11:41 Some questions about userspace control elements Takashi Sakamoto
2015-02-01 17:50 ` Clemens Ladisch
2015-02-02 14:14   ` Takashi Sakamoto
2015-02-04 23:51   ` Takashi Sakamoto
2015-02-05  0:44     ` Takashi Sakamoto
2015-02-06  9:38       ` Clemens Ladisch
2015-02-07  1:58         ` Takashi Sakamoto
2015-02-07 15:45           ` Clemens Ladisch
2015-02-08 10:57             ` Takashi Sakamoto [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=54D74115.4070202@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.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.