From: Mark Brown <broonie@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 2/3] ASoC: topology: Add topology core
Date: Wed, 27 May 2015 20:48:27 +0100 [thread overview]
Message-ID: <20150527194827.GP21577@sirena.org.uk> (raw)
In-Reply-To: <55661997.2050800@metafoo.de>
[-- Attachment #1.1: Type: text/plain, Size: 931 bytes --]
On Wed, May 27, 2015 at 09:23:03PM +0200, Lars-Peter Clausen wrote:
> Ideally we'd turn the dependency chain the other way around and have a
> snd_soc_dobj_widget struct which inherits snd_soc_dapm_widget and
> snd_soc_dobj. In the dobj callbacks you can then still use container_of to
> get it. This comes at the expense that we have to add a free() callback to
> snd_soc_dapm_widget. But it opens up the possibility to have other
> specialized widgets sub-classes. snd_soc_dapm_widget is already rather large
> given how many instance we have of it and quite a few of the fields are only
> used by a particular type of widget. Another good candidate for example
> would be the DAI link widget with all its params fields.
Yeah, I was thinking something along those lines might be good long term
but it's definitely a separate thing to getting the topology stuff in
and I started worrying about things like multiple inheritance.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-05-27 19:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 17:22 [PATCH v2 1/3] ASoC: topology: Add topology UAPI header Liam Girdwood
2015-05-25 17:22 ` [PATCH v2 2/3] ASoC: topology: Add topology core Liam Girdwood
2015-05-27 19:00 ` Mark Brown
2015-05-27 19:23 ` Lars-Peter Clausen
2015-05-27 19:48 ` Mark Brown [this message]
2015-05-28 14:45 ` Liam Girdwood
2015-05-28 15:23 ` Mark Brown
2015-05-28 14:33 ` Liam Girdwood
2015-05-29 5:57 ` Vinod Koul
2015-05-25 17:22 ` [PATCH v2 3/3] ALSA: topology: Export ID types for TLV controls Liam Girdwood
2015-05-28 14:47 ` Liam Girdwood
2015-05-28 14:59 ` Takashi Iwai
2015-05-26 10:33 ` [PATCH v2 1/3] ASoC: topology: Add topology UAPI header 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=20150527194827.GP21577@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lars@metafoo.de \
--cc=liam.r.girdwood@linux.intel.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