From: Liam Girdwood <lrg@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 3/4] ASoC: firmware core: Add core support for dynamic kcontrols and widgets.
Date: Tue, 20 Nov 2012 12:19:28 +0000 [thread overview]
Message-ID: <50AB7550.7020804@ti.com> (raw)
In-Reply-To: <20121120023606.GB4483@opensource.wolfsonmicro.com>
On 20/11/12 02:36, Mark Brown wrote:
> On Mon, Nov 19, 2012 at 06:12:44PM +0000, Liam Girdwood wrote:
>
>> @@ -584,6 +584,8 @@ struct snd_soc_dapm_widget {
>> int num_kcontrols;
>> const struct snd_kcontrol_new *kcontrol_news;
>> struct snd_kcontrol **kcontrols;
>> + int denum;
>> + int dmixer;
>
> In the patch adding the actual functional code it looks like these are
> just treated as booleans saying if the control is dynamic. This in
> conjunction with the fact that we've got a single list of dynamic
> controls means that we can only have one block of dynamic controls on
> this device. Is that correct? If not then I've got the wrong end of
> the stick otherwise...
>
That's correct atm.
> It occurs to me that if we just assign these to numbers per thing with
> firmware then we can easily use this data structure to support multiple
> firmwares per device. We just go through the list and delete all mixers
> numbered 1 or something. If we do that I think we can simplify the code
> a little and just make all the mixers and controls "dynamic", using ID 0
> for the non-changable ones.
>
Good idea. I'll make this change.
Liam
next prev parent reply other threads:[~2012-11-20 12:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 18:12 [PATCH 1/4] ASoC: firmware: Add support for FW based kcontrols Liam Girdwood
2012-11-19 18:12 ` [PATCH 2/4] ASoC: firmware: Add support for FW based widgets Liam Girdwood
2012-11-20 2:16 ` Mark Brown
2012-11-19 18:12 ` [PATCH 3/4] ASoC: firmware core: Add core support for dynamic kcontrols and widgets Liam Girdwood
2012-11-20 2:36 ` Mark Brown
2012-11-20 12:19 ` Liam Girdwood [this message]
2012-11-19 18:12 ` [PATCH 4/4] ASoC: firmware core: Add core support to create and destroy firmware components Liam Girdwood
2012-11-19 18:46 ` Takashi Iwai
2012-11-20 12:03 ` Liam Girdwood
2012-11-20 12:05 ` Takashi Iwai
2012-11-21 0:30 ` Mark Brown
2012-11-21 6:43 ` Takashi Iwai
2012-11-21 6:49 ` Mark Brown
2012-11-20 3:27 ` Mark Brown
2012-11-20 15:14 ` Liam Girdwood
2012-11-21 0:43 ` Mark Brown
2012-11-21 10:21 ` Liam Girdwood
2012-11-21 10:37 ` Mark Brown
2012-11-21 11:16 ` Liam Girdwood
2012-11-21 11:52 ` Mark Brown
2012-11-19 18:36 ` [PATCH 1/4] ASoC: firmware: Add support for FW based kcontrols Takashi Iwai
2012-11-29 12:08 ` Liam Girdwood
2012-11-29 15:15 ` Takashi Iwai
2012-11-29 15:51 ` Liam Girdwood
2012-11-29 16:01 ` Liam Girdwood
2012-11-29 17:35 ` Takashi Iwai
2012-11-29 17:39 ` Liam Girdwood
2012-11-20 2:11 ` Mark Brown
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=50AB7550.7020804@ti.com \
--to=lrg@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
/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