From: Jarkko Nikula <jhnikula@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [RFC] ASoC: multi-component: Add optional kcontrol prefix name for a DAI link
Date: Mon, 30 Aug 2010 14:17:29 +0300 [thread overview]
Message-ID: <20100830141729.75388459.jhnikula@gmail.com> (raw)
In-Reply-To: <20100826133229.GA3803@opensource.wolfsonmicro.com>
On Thu, 26 Aug 2010 14:32:29 +0100
Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> On Wed, Aug 25, 2010 at 01:59:22PM +0300, Jarkko Nikula wrote:
>
> > I went back to original idea that prefixes only kcontrols of codec and
> > doesn't add any new API. So if we can have DAIless codec drivers (i.e.
> > amplifiers) then there is no immediate need for prefixing widgets and
> > routes.
>
> Note that even DAIless drivers can have routing in them - see WM9090 for
> example.
>
I don't see it are there any problems. For me it looks the routes in
WM9090 are unique and registered to own codec instance so there should
not be route prefixing needed.
How these amplifier drivers are actually meant to be probed? Currently
struct snd_soc_codec_driver->probe is called only from
soc_probe_dai_link.
--
Jarkko
next prev parent reply other threads:[~2010-08-30 11:16 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 [this message]
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
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=20100830141729.75388459.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).