From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: anish kumar <yesanishhere@gmail.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Charles <Charles.Keepax@cirrus.com>
Subject: Re: DAPM: codec to codec link documentation[RFC]
Date: Mon, 26 Sep 2016 09:46:08 +0100 [thread overview]
Message-ID: <20160926084608.GW21682@localhost.localdomain> (raw)
In-Reply-To: <CABCoZhC6OhDo90+WzVzSs8xcr8VmWjkAPdsdNG4fsWQJf0v9GA@mail.gmail.com>
On Sun, Sep 25, 2016 at 10:53:25PM -0700, anish kumar wrote:
> On Thu, Sep 15, 2016 at 1:33 AM, Charles Keepax
> <ckeepax@opensource.wolfsonmicro.com> wrote:
> > On Wed, Sep 14, 2016 at 12:08:56PM -0700, anish kumar wrote:
> >> {
> >> .name = "your_name",
> >> .stream_name = "your_stream_name",
> >> .cpu_dai_name = "snd-soc-dummy-dai",
> >> .codec_name = "codec-2,
> >> .codec_dai_name = "codec-2-dai_name",
> >> .dai_fmt = SND_SOC_DAIFMT_I2S | SND_SOC_DAIFMT_NB_NF
> >> | SND_SOC_DAIFMT_CBM_CFM,
> >> .ignore_suspend = 1,
> >> .params = &dummy_params,
> >> },
> >> {
> >> .name = "your_name",
> >> .stream_name = "your_stream_name",
> >> .cpu_dai_name = "snd-soc-dummy-dai",
> >> .codec_name = "codec-3,
> >> .codec_dai_name = "codec-3-dai_name",
> >> .dai_fmt = SND_SOC_DAIFMT_I2S | SND_SOC_DAIFMT_NB_NF
> >> | SND_SOC_DAIFMT_CBM_CFM,
> >> .ignore_suspend = 1,
> >> .params = &dummy_params,
> >> },
> >>
> >
> > Probably worth having a look at DT options as well, not sure how
> > well would be supported for c2c links at the mo but probably
> > worth mentioning something about it.
>
> I didn't get you. Do you mean using DT option to specify if
> a particular node is c2c?
I just mean that most machine drivers these days specify at least
part of the DAI link configuration through device tree. I don't
know off the top of my head what support is currently provided for
codec to codec links in DT, my suspicion is none. So it might be
worth at least noting that.
Thanks,
Charles
prev parent reply other threads:[~2016-09-26 8:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 19:08 DAPM: codec to codec link documentation[RFC] anish kumar
2016-09-15 8:33 ` Charles Keepax
2016-09-26 5:53 ` anish kumar
2016-09-26 8:46 ` Charles Keepax [this message]
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=20160926084608.GW21682@localhost.localdomain \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=Charles.Keepax@cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=yesanishhere@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;
as well as URLs for NNTP newsgroup(s).