[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c1c56c52-656c-cc06-02d1-abefd330ebc8@nxp.com>
Date: Tue, 25 Feb 2020 13:39:43 +0000
From: Daniel Baluta <daniel.baluta@....com>
To: Fabio Estevam <festevam@...il.com>,
"Daniel Baluta (OSS)" <daniel.baluta@....nxp.com>
CC: "broonie@...nel.org" <broonie@...nel.org>,
"tiwai@...e.com" <tiwai@...e.com>,
"Xiubo.Lee@...il.com" <Xiubo.Lee@...il.com>,
Viorel Suman <viorel.suman@....com>,
"S.j. Wang" <shengjiu.wang@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
dl-linux-imx <linux-imx@....com>,
"peter.ujfalusi@...com" <peter.ujfalusi@...com>,
"pierre-louis.bossart@...ux.intel.com"
<pierre-louis.bossart@...ux.intel.com>,
"kuninori.morimoto.gx@...esas.com" <kuninori.morimoto.gx@...esas.com>
Subject: Re: [PATCH] ASoC: fsl: Add generic CPU DAI driver
On 25.02.2020 15:29, Fabio Estevam wrote:
> On Tue, Jan 28, 2020 at 11:47 AM Daniel Baluta (OSS)
> <daniel.baluta@....nxp.com> wrote:
>
>> +static struct snd_soc_dai_driver fsl_esai_dai = {
>> + .name = "esai0",
>> +};
>> +
>> +static struct snd_soc_dai_driver fsl_sai_dai = {
>> + .name = "sai1",
> So the name will be hardcoded to sai1 even if SAI2, SAI3, etc is used?
Indeed this is a good point. In our use case with DSP we are only using
SAI1/ESAI0 for now.
Let me try to get a more generic approach and resend.
thanks,
Daniel.
Powered by blists - more mailing lists