From: Jarkko Nikula <jhnikula@gmail.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: alsa-devel@alsa-project.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: [RFC] ASoC: multi-component: Add optional kcontrol prefix name for a DAI link
Date: Fri, 3 Sep 2010 14:20:47 +0300 [thread overview]
Message-ID: <20100903142047.c70c21c8.jhnikula@gmail.com> (raw)
In-Reply-To: <1283508057.3069.46.camel@odin>
On Fri, 03 Sep 2010 11:00:57 +0100
Liam Girdwood <lrg@slimlogic.co.uk> wrote:
> > I think I'd like a firm idea of how the cross device DAPM works before
> > we do anything with the prefixes since there's some overlap there (if
> > only due to the fact that half the controls come from DAPM), even if the
> > cross device DAPM doesn't actually work yet. I think your current code
> > is probably going to work well with DAPM but I need to have a bit of a
> > think about that over the weekend.
>
Ok, sounds good. Doing DAPM first avoids that there is no then need to
go back and forth with prefixing.
> I've made some initial progress here with DAPM by de-coupling it from
> CODEC drivers. So I now have a struct dapm_context * in the codec,
> platform and machine drivers. I just now need to get some time to
> experiment with the best way to hook them all up.
>
> It's currently in my L24.9 branch, although the patches are in need of
> clean up and squashing so are not ready for upstream yet.
>
Thanks for info. Have to give a try to it :-)
--
Jarkko
prev parent reply other threads:[~2010-09-03 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 7:29 [RFC] ASoC: multi-component: Add optional kcontrol prefix name for a DAI link Jarkko Nikula
2010-08-16 10:07 ` Mark Brown
2010-08-16 10:53 ` Jarkko Nikula
2010-08-16 11:09 ` Mark Brown
2010-08-19 11:44 ` Jarkko Nikula
2010-08-19 13:54 ` Mark Brown
2010-08-19 15:20 ` Jarkko Nikula
2010-08-20 8:51 ` Jarkko Nikula
2010-08-23 14:46 ` Jarkko Nikula
2010-08-23 15:21 ` Mark Brown
2010-08-24 7:23 ` Jarkko Nikula
2010-08-24 10:10 ` Mark Brown
2010-08-25 10:59 ` Jarkko Nikula
2010-08-26 13:32 ` Mark Brown
2010-08-30 11:17 ` Jarkko Nikula
2010-09-02 14:25 ` Mark Brown
2010-09-03 7:55 ` Jarkko Nikula
2010-09-03 9:33 ` Mark Brown
2010-09-03 10:00 ` Liam Girdwood
2010-09-03 11:20 ` Jarkko Nikula [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=20100903142047.c70c21c8.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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).