[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pn7ofs19.wl-kuninori.morimoto.gx@renesas.com>
Date: 18 Aug 2020 14:23:39 +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>,
<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 v2 3/9] ASoC: audio-graph: Identify 'no_pcm' DAI links for DPCM
Hi again
> PCM devices are created for FE dai links with 'no-pcm' flag as '0'.
> Such DAI links have CPU component which implement either pcm_construct()
> or pcm_new() at component or dai level respectively. Based on this,
> current patch exposes a helper function to identify such components
> and populate 'no_pcm' flag for DPCM DAI link.
>
> This helps to have BE<->BE component links where PCM devices need
> not be created for CPU component involved in such links.
>
> Signed-off-by: Sameer Pujar <spujar@...dia.com>
> ---
(snip)
> +static bool soc_component_is_pcm(struct snd_soc_dai_link_component *dlc)
> +{
> + struct snd_soc_dai *dai = snd_soc_find_dai(dlc);
> +
> + if (dai && (dai->component->driver->pcm_construct ||
> + dai->driver->pcm_new))
> + return true;
> +
> + return false;
> +}
This snd_soc_find_dai() will indicate WARNING
if .config has CONFIG_LOCKDEP for me.
Maybe implement it at soc-core.c with client_mutex lock
is needed.
Thank you for your help !!
Best regards
---
Kuninori Morimoto
Powered by blists - more mailing lists