From: Jean-Francois Moine <moinejf@free.fr>
To: Mark Brown <broonie@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH] ASoC: generic: add generic compound card with DT support
Date: Thu, 2 Jan 2014 12:43:31 +0100 [thread overview]
Message-ID: <20140102124331.2bcfc172@armhf> (raw)
In-Reply-To: <20140102111056.GT31886@sirena.org.uk>
On Thu, 2 Jan 2014 11:10:56 +0000
Mark Brown <broonie@kernel.org> wrote:
> On Thu, Jan 02, 2014 at 10:26:47AM +0100, Jean-Francois Moine wrote:
>
> > /* audio */
> > port@1 {
> > hdmi_i2s_audio: endpoint@0 {
> > reg = <0x03>;
> > remote-endpoint = <&audio_hdmi_i2s>;
> > };
>
> I think we want an explicit object in the card representing the DAIs.
> This will both be useful for making it easy to find the configuration
> for the link and will be more extensible for the cases where multiple
> devices are connected, you can't just assume there's just two.
I don't see the problem: the 'port' is the DAI. The associated
endpoints give the DAI links and the routing information.
As the DT definition has been done for video, some properties may be
added at will for audio.
What kind of object were you thinking of?
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2014-01-02 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131231113138.102044cf@armhf>
[not found] ` <52C466E1.3030302@metafoo.de>
[not found] ` <20140101210814.31e3f3a9@armhf>
[not found] ` <52C4766B.8080000@metafoo.de>
2014-01-02 9:26 ` [alsa-devel] [PATCH] ASoC: generic: add generic compound card with DT support Jean-Francois Moine
2014-01-02 11:10 ` Mark Brown
2014-01-02 11:43 ` Jean-Francois Moine [this message]
2014-01-02 11:56 ` Mark Brown
2014-01-02 12:44 ` Jean-Francois Moine
2014-01-02 13:10 ` Mark Brown
2014-01-02 17:50 ` Jean-Francois Moine
2014-01-02 18:35 ` [alsa-devel] " 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=20140102124331.2bcfc172@armhf \
--to=moinejf@free.fr \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.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).