From: Jean-Francois Moine <moinejf@free.fr>
To: Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Lars-Peter Clausen <lars@metafoo.de>
Subject: ASoC:simple-card: problem with multi-DAIs
Date: Tue, 2 Sep 2014 09:00:05 +0200 [thread overview]
Message-ID: <20140902090005.4a2c80b2@armhf> (raw)
Hi Kuninori,
In your patch
ASoC: simple-card: remove dai_link->cpu_dai_name when DT
(commit 179949bc04c7157a4b2279f62a842638b61f78f9
in /kernel/git/broonie/sound.git/)
you removed all 'cpu_dai_name's, and this creates problems in my system.
I have an audio controller with 2 DAIs. The audio system is defined as:
sound {
compatible = "simple-audio-card";
simple-audio-card,name = "Cubox Audio";
simple-audio-card,dai-link@0 { /* I2S - HDMI */
format = "i2s";
cpu {
sound-dai = <&audio1 0>;
};
codec {
sound-dai = <&hdmi 0>;
};
};
simple-audio-card,dai-link@1 { /* S/PDIF - HDMI */
cpu {
sound-dai = <&audio1 1>;
};
codec@0 {
sound-dai = <&hdmi 1>;
};
};
...
}
The 'cpu_of_node' of both CPU DAIs is the same ('audio1'), and only the
cpu_dai_name permits to know the CPU DAI.
But, as you removed it, both DAI links are built with the 1st CPU DAI
(I2S), and the second link (via S/PDIF) does not work.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2014-09-02 6:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 7:00 Jean-Francois Moine [this message]
2014-09-02 11:03 ` ASoC:simple-card: problem with multi-DAIs Kuninori Morimoto
2014-09-02 11:05 ` [PATCH][RFC] ASoC: simple-card: fixup cpu_dai_name clear case Kuninori Morimoto
2014-09-02 18:00 ` Jean-Francois Moine
2014-09-03 12:54 ` 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=20140902090005.4a2c80b2@armhf \
--to=moinejf@free.fr \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=lars@metafoo.de \
/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.