alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Dimitris Papastamos <dp@opensource.wolfsonmicro.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, broonie@kernel.org,
	patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH 2/3] ASoC: wm_adsp: Add support for	grouped ALSA binary controls
Date: Fri, 1 Nov 2013 10:46:27 +0000	[thread overview]
Message-ID: <20131101104627.GA5396@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <s5htxfxj2ly.wl%tiwai@suse.de>

On Thu, Oct 31, 2013 at 08:55:53AM +0100, Takashi Iwai wrote:
> At Wed, 30 Oct 2013 16:54:29 +0000,
> Dimitris Papastamos wrote:
> > 
> > Currently the ALSA ABI imposes a hard limit of 512 bytes per binary
> > control.  To support coefficient data blocks of larger sizes we carve up
> > this space into multiple alsa controls.  All of these controls are
> > identified by a common prefix and suffix of the form ":<blk id>".
> > 
> > Control groupings can also consist of a single block in which case the
> > suffix ":0" is used.
> 
> Why not using the control element index?
> 
> You can create each kctl element individually with a different index,
> but also you can create multiple ctl elements in a single shot by
> passing to snd_kcontrol_new.count field.  This will create a grouped 
> object, thus it saves spaces, too, in comparison with individual
> kctls.  The drawback is that you need to retrieve the real index via
> snd_ctl_get_ioff*() in each control callback.

I will give this a shot when I have some time and re-send the patch.

Thanks,
Dimitris

      reply	other threads:[~2013-11-01 10:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 16:54 [PATCH 1/3] ASoC: wm_adsp: Print error when regmap reads/writes fail Dimitris Papastamos
2013-10-30 16:54 ` [PATCH 2/3] ASoC: wm_adsp: Add support for grouped ALSA binary controls Dimitris Papastamos
2013-10-31  7:55   ` Takashi Iwai
2013-11-01 10:46     ` Dimitris Papastamos [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=20131101104627.GA5396@opensource.wolfsonmicro.com \
    --to=dp@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=patches@opensource.wolfsonmicro.com \
    --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).