From: Arnaud Pouliquen <arnaud.pouliquen@st.com>
To: alsa-devel@alsa-project.org
Cc: Mark Brown <broonie@kernel.org>, lgirdwood@gmail.com
Subject: Re: [RFC] question regarding codec DAI ops
Date: Mon, 23 Jun 2014 09:30:19 +0200 [thread overview]
Message-ID: <53A7D78B.1050508@st.com> (raw)
In-Reply-To: <20140621102644.GQ5099@sirena.org.uk>
On 06/21/2014 12:26 PM, Mark Brown wrote:
> On Fri, Jun 20, 2014 at 04:07:03PM +0200, Arnaud Pouliquen wrote:
>
>> I have a platform with several audio IOs (DAC , HDMI...) and I2S In/out
>> connectors.
>> I'm using my codec driver but for this I2S output i used dummy codec driver
>> with the snd-soc-dummy-dai dai.
> Why are you using the dummy driver? This is intended to stub things out
> in some DPCM situations rather than as something that should be used in
> normal code.
My platform is a base for several projects and customers. In this
context some extra I2S bus are available for extensions.
I have two use cases to support.
- Possibility to test I2S bus without audio codec associated.
- Support client that does not use ASOC for audio codec ( a.e one
manage HDMI in his display driver...)
To be able to support these use cases i use device tree to construct the
alsa card. if no asoc codec present, i connect dummy one.
If customer want to use another codec they have just to change device
tree.
Here is an example of my device tree declaration.
sound {
compatible = "st,snd-soc-sti";
st,card-name = "audio";
st,audio-routing =
/* Analog out route */
"Analog out","DAC",
"DAC","dac_p";
st,asoc-platform = <&sti_asoc_platform>;
backend-name = "HDMI_out", "PCM_out",
"Analog_out", "spdif",
"HDMI_in", "PCM_in";
backend-cpu-dai = <&snd_uni_player0 &snd_uni_player1
&snd_uni_player2 &snd_uni_player3
&snd_uni_reader0 &snd_uni_reader1 >;
backend-codec = <&sti_sasg_codec 0
&sti_sasg_codec &sti_sasg_codec
0 0>;
backend-codec-dai = "sas-dai-hdmi-out", "snd-soc-dummy-dai",
"sas-dai-dac", "sas-dai-spdif-out",
"snd-soc-dummy-dai","snd-soc-dummy-dai";
};
backend-codec specify the codec driver. If 0 dummy codec is used.
>
>> From your point of view, what should be best solution?
> I think we need to take a step back and work out what the goal is here.
next prev parent reply other threads:[~2014-06-23 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 14:07 [RFC] question regarding codec DAI ops Arnaud Pouliquen
2014-06-21 10:26 ` Mark Brown
2014-06-23 7:30 ` Arnaud Pouliquen [this message]
2014-06-30 10:31 ` Mark Brown
2014-07-01 9:28 ` Arnaud Pouliquen
2014-07-01 10:14 ` 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=53A7D78B.1050508@st.com \
--to=arnaud.pouliquen@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox