All of lore.kernel.org
 help / color / mirror / Atom feed
From: Abramo Bagnara <abramo@alsa-project.org>
To: Paul Davis <pbd@op.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: how to define a 2-index control element?
Date: Sat, 04 May 2002 15:18:27 +0200	[thread overview]
Message-ID: <3CD3DFA3.4395E0B4@alsa-project.org> (raw)
In-Reply-To: 200205041245.g44Cjgq07507@op.net

Paul Davis wrote:
> 
> i'm looking at the control API, and i can't see how to define a
> control that requires 2 values in order to read or write the control.
> 
> there seems to be an assumption that a control element maps 1:1 onto a
> hardware entity. i want (need) to create a control element that is
> more flexible than that. the basic idea is:
> 
>          control->value.integer.value[0] = source;
>          control->value.integer.value[1] = destination;
> 
>          snd_ctl_read (...)
> 
> or:
> 
>          control->value.integer.value[0] = source;
>          control->value.integer.value[1] = destination;
>          control->value.integer.value[3] = gain;
> 
>          snd_ctl_write (...)
> 
> am i missing something really simple?
> 

I suggest you to use the field index of struct sndrv_ctl_elem_id (one
byte per dimension).

id.index = (source << 8) | destination;


-- 
Abramo Bagnara                       mailto:abramo@alsa-project.org

Opera Unica                          Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy

ALSA project               http://www.alsa-project.org
It sounds good!

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

  reply	other threads:[~2002-05-04 13:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-04 12:45 how to define a 2-index control element? Paul Davis
2002-05-04 13:18 ` Abramo Bagnara [this message]
2002-05-05 13:48   ` Paul Davis
2002-05-05 15:50     ` Jaroslav Kysela
2002-05-06  1:32       ` Paul Davis
2002-05-06  6:46         ` Jaroslav Kysela
2002-05-06 11:22           ` Paul Davis
2002-05-06 11:44             ` Jaroslav Kysela
2002-05-06 12:03         ` Takashi Iwai
2002-05-06 12:19           ` Abramo Bagnara
2002-05-06 12:53             ` Takashi Iwai
2002-05-06 19:11               ` Abramo Bagnara
2002-05-07  9:29                 ` Takashi Iwai
2002-05-07  9:55                   ` Jaroslav Kysela
2002-05-07 10:34                     ` Takashi Iwai
2002-05-07 17:17                       ` Paul Davis
2002-05-07 22:06                         ` Abramo Bagnara
2002-05-08  0:00                           ` Paul Davis
     [not found] <20020508000005.EB5AC59D35D@kerberos.suse.cz>
2002-05-08  7:52 ` Jaroslav Kysela
2002-05-08  9:52   ` Takashi Iwai

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=3CD3DFA3.4395E0B4@alsa-project.org \
    --to=abramo@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=pbd@op.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 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.