[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <877dvq1yhy.wl-kuninori.morimoto.gx@renesas.com>
Date: 29 Jun 2020 09:56:27 +0900
From: Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>
To: Sameer Pujar <spujar@...dia.com>
Cc: <broonie@...nel.org>, <perex@...ex.cz>, <tiwai@...e.com>,
<robh+dt@...nel.org>, <lgirdwood@...il.com>,
<thierry.reding@...il.com>, <jonathanh@...dia.com>,
<digetx@...il.com>, <alsa-devel@...a-project.org>,
<linux-tegra@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<sharadg@...dia.com>, <mkumard@...dia.com>,
<viswanathl@...dia.com>, <rlokhande@...dia.com>,
<dramesh@...dia.com>, <atalambedu@...dia.com>,
<nwartikar@...dia.com>, <swarren@...dia.com>,
<nicoleotsuka@...il.com>
Subject: Re: [PATCH v4 10/23] ASoC: simple-card: Wrong daifmt for CPU end of DPCM DAI link
Hi Sameer
> simple-audio-card,dai-link@xxx {
> format = "i2s";
> bitclock-master=<&cpu1>;
> frame-master=<&cpu1>;
>
> cpu1: cpu@0 {
> ...
> };
>
> codec@0 {
> ...
> };
>
> ...
> };
>
> In above case CPU is expected to be configured as a master and Codec as
> a slave device. But both CPU/Codec are being configured as slave devices.
> This happens because asoc_simple_parse_daifmt() uses Codec reference and
> sets up the 'dai_link->dai_fmt' accordingly while parsing both CPU and
> Codec.
I'm sorry but I don't 100% understand about this case...
asoc_simple_parse_daifmt() should work in this case
The reason why it needs codec node is that
SND_SOC_DAIFMT_CBx_CFx are "Codec" base Master/Slave.
Thank you for your help !!
Best regards
---
Kuninori Morimoto
Powered by blists - more mailing lists