From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Timur Tabi <timur.tabi@gmail.com>
Cc: alsa-devel mailing list <alsa-devel@alsa-project.org>,
Mark Brown <broonie@sirena.org.uk>
Subject: Re: asoc multi-component: almost there!
Date: Tue, 27 Jul 2010 14:49:06 +0100 [thread overview]
Message-ID: <1280238546.3085.89.camel@odin> (raw)
In-Reply-To: <AANLkTimKhtzu-_Sts3AkVmDhc19tOGg4dqMGzdCro=A7@mail.gmail.com>
On Mon, 2010-07-26 at 17:37 -0500, Timur Tabi wrote:
> Liam,
>
> I almost got it working. I can generate names that match, so it finds it:
>
> soc_bind_dai_link:1136 cpu_dai->name=e0016000.ssi,
> dai_link->cpu_dai_name=e0016000.ssi
> soc_bind_dai_link:1159 codec->name=cs4270-codec.0-004f,
> dai_link->codec_name=cs4270-codec.0-004f
> soc_bind_dai_link:1169 codec_dai->name=e0016000.ssi,
> dai_link->codec_dai_name=cs4270-hifi
> soc_bind_dai_link:1169 codec_dai->name=cs4270-hifi,
> dai_link->codec_dai_name=cs4270-hifi
> soc_bind_dai_link:1194 platform->name=e0021180.dma-channel,
> dai_link->platform_name=e0021100.dma-channel
> soc_bind_dai_link:1194 platform->name=e0021100.dma-channel,
> dai_link->platform_name=e0021100.dma-channel
> soc_bind_dai_link:1136 cpu_dai->name=e0016000.ssi,
> dai_link->cpu_dai_name=e0016000.ssi
> soc_bind_dai_link:1159 codec->name=cs4270-codec.0-004f,
> dai_link->codec_name=cs4270-codec.0-004f
> soc_bind_dai_link:1169 codec_dai->name=e0016000.ssi,
> dai_link->codec_dai_name=cs4270-hifi
> soc_bind_dai_link:1169 codec_dai->name=cs4270-hifi,
> dai_link->codec_dai_name=cs4270-hifi
> soc_bind_dai_link:1194 platform->name=e0021180.dma-channel,
> dai_link->platform_name=e0021180.dma-channel
> asoc: cs4270-hifi <-> e0016000.ssi mapping ok
>
> but then I get this:
>
> sysfs: cannot create duplicate filename '/devices/platform/soc-audio/cs4270'
>
> I'm registering two DAIs -- one for playback, one for capture, but I'm
> using the same name for the codec DAI. How do I resolve this?
>
Ah ok, I thought you meant two CODEC DAIs earlier rather than two
machine DAI links.
Each machine DAI link now has a sysfs entry so we can inspect its
configuration/status now. Hence each machine DAI link must be named
differently. You could have a "cs4270 playback" and "cs4270 capture" DAI
links now.
Thanks
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-07-27 13:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 22:37 asoc multi-component: almost there! Timur Tabi
2010-07-27 10:42 ` Liam Girdwood
2010-07-27 13:07 ` Timur Tabi
2010-07-27 13:49 ` Liam Girdwood [this message]
2010-07-27 15:20 ` Timur Tabi
2010-07-27 17:26 ` Liam Girdwood
2010-07-27 18:20 ` Timur Tabi
2010-07-27 18:45 ` Mark Brown
2010-07-27 21:23 ` Timur Tabi
2010-07-28 14:07 ` Liam Girdwood
2010-07-28 20:12 ` Timur Tabi
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=1280238546.3085.89.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@sirena.org.uk \
--cc=timur.tabi@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.