From: Raffaele Recalcati <lamiaposta71@gmail.com>
To: alsa-devel@alsa-project.org
Subject: double dai question and analog paths
Date: Fri, 31 Aug 2012 19:11:34 +0200 [thread overview]
Message-ID: <CAFU7RzOo14teckc404GP+Q2SdTMn93xDeTNPGUnwtWAws7eRGw@mail.gmail.com> (raw)
I can play succesfully each of the following substreams:
static struct snd_soc_dai_link omap3baia_dai[] = {
{
.name = "TLV320AIC31",
.stream_name = "AIC31",
.cpu_dai_name = "omap-mcbsp-dai.3",
.codec_dai_name = "tlv320aic3x-hifi",
.platform_name = "omap-pcm-audio",
.codec_name = "tlv320aic3x-codec.2-0018",
.init = omap3baia_tlvaic31_init,
.ops = &omap3baia_tlvaic31_ops,
},
{
.name = "TWL4030",
.stream_name = "TWL4030",
.cpu_dai_name = "omap-mcbsp-dai.1",
.platform_name = "omap-pcm-audio",
.codec_dai_name = "twl4030-hifi",
.codec_name = "twl4030-codec",
.init = omap3baia_twl4030_init,
.ops = &omap3baia_twl4030_ops,
},
};
I have also some analog connections between TWL4030 and TLV320AIC31
and I'd like to create an automatic audio path (for example from
TWL4030 HFL to TLV320AIC31 LINE2L), but I obtain
"Failed to add route Virtual Tps to Tlv->LINE2L"
static const struct snd_soc_dapm_route audio_map_twl4030[] = {
{"Virtual Tps to Tlv", NULL, "HFL"}, /* from tps to tlv */
{"LINE2L", NULL, "Virtual Tps to Tlv"}, /* from tps to tlv */
};
Because LINE2L is obviously defined inside TWL4030 codec.
static const struct snd_soc_dapm_widget dapm_widgets_twl4030[] = {
SND_SOC_DAPM_OUTPUT("Virtual Tps to Tlv"),
};
Is there a clean way to manage this situation?
I have also tried without "Virtual Tps to Tlv" but the problem is the same.
Thx,
Raffaele
reply other threads:[~2012-08-31 17:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAFU7RzOo14teckc404GP+Q2SdTMn93xDeTNPGUnwtWAws7eRGw@mail.gmail.com \
--to=lamiaposta71@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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).