From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Mark Brown <broonie@kernel.org>
Cc: Sameer Pujar <spujar@nvidia.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: More Generic Audio Graph Sound Card idea
Date: 16 Oct 2020 08:04:37 +0900 [thread overview]
Message-ID: <87pn5j3xiu.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <20201015143254.GC4390@sirena.org.uk>
Hi Mark
Thank you for feedback
> > -- DT Image --
> >
> > +--+
> > => | |<--> Codec1
> > | |<--> Codec2
> > +--+
> >
> > -- DT Sample --
> >
> > sound {
> > compatible = "audio-graph-card2";
> >
> > dais = <&codec2codec>;
> > };
> >
> > CODEC2CODEC {
> > compatible = "audio-graph-card2-codec2codec";
> >
> > ports {
> > codec2codec: port@0 { fe_ep: endpoint { remote-endpoint = <&codec1_ep>; }; };
> > port@1 { be_ep: endpoint { remote-endpoint = <&codec2_ep>; }; };
> > };
> > };
>
> I'm a bit confused about the use of FE and BE here since the two CODECs
> are peers rather than this being DPCM - I think that's just a bit
> cut'n'paste rather than anything else though? The other examples look
> sensible I think but this one feels odd.
FE here is indicating CPU part's Codec,
BE is for Codec part's Codec.
> > -- Image ---
> >
> > *******
> > PCM0 <--> * * <--> DAI0: Codec Headset
> > PCM1 <--> * * <--> DAI1: Codec Speakers
> > PCM2 <--> * DSP * <--> DAI2: MODEM
> > PCM3 <--> * * <--> DAI3: BT
> > * * <--> DAI4: DMIC
> > * * <--> DAI5: FM
> > *******
>
> > DSP {
> > compatible = "audio-graph-card2-dsp";
> >
> > ports@0 {
> > /* Front-End is pcm0_ep, Back-End is dummy */
> > dsp_fe0: port@0 { dsp_fe0_ep: endpoint { remote-endpoint = <&pcm0_ep>; }; };
> > port@1 { };
> > };
>
> I'm not clear why we need to represent the dummy port here?
I'm thining that
port@0 is IN (= CPU), port@1 is OUT (= Codec).
Empty endpoint means not yet connected (= dummy).
It is difficut to know it was CPU-dummy or dummy-Codec without it.
Thank you for your help !!
Best regards
---
Kuninori Morimoto
prev parent reply other threads:[~2020-10-15 23:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 4:15 More Generic Audio Graph Sound Card idea Kuninori Morimoto
2020-08-21 5:26 ` Sameer Pujar
2020-08-21 7:14 ` Kuninori Morimoto
2020-08-21 8:28 ` Sameer Pujar
2020-08-21 13:02 ` Mark Brown
2020-09-25 1:43 ` Kuninori Morimoto
2020-09-25 19:22 ` Mark Brown
2020-09-25 20:04 ` Pierre-Louis Bossart
2020-09-25 20:10 ` Mark Brown
2020-09-25 20:50 ` Pierre-Louis Bossart
2020-08-21 7:11 ` Daniel Baluta
2020-08-21 7:25 ` Kuninori Morimoto
2020-08-21 7:33 ` Daniel Baluta
2020-08-21 11:47 ` Mark Brown
2020-08-21 12:18 ` Mark Brown
2020-08-24 0:25 ` Kuninori Morimoto
2020-08-24 6:25 ` Sameer Pujar
2020-08-25 0:59 ` Kuninori Morimoto
2020-08-25 3:11 ` Sameer Pujar
2020-08-25 5:13 ` Kuninori Morimoto
2020-08-25 5:42 ` Sameer Pujar
2020-08-25 6:35 ` Kuninori Morimoto
2020-08-26 6:46 ` Sameer Pujar
2020-08-27 1:18 ` Kuninori Morimoto
2020-08-27 1:36 ` Kuninori Morimoto
2020-09-03 23:51 ` Kuninori Morimoto
2020-09-09 11:33 ` Sameer Pujar
2020-08-21 15:49 ` Pierre-Louis Bossart
2020-10-13 4:50 ` Kuninori Morimoto
2020-10-15 14:32 ` Mark Brown
2020-10-15 23:04 ` Kuninori Morimoto [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=87pn5j3xiu.wl-kuninori.morimoto.gx@renesas.com \
--to=kuninori.morimoto.gx@renesas.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=spujar@nvidia.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 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.