[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6c2bb431-c7d5-53b7-2f62-c1487e321680@nvidia.com>
Date: Sat, 29 Aug 2020 16:22:09 +0530
From: Sameer Pujar <spujar@...dia.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@...esas.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 Morimoto-san,
Sorry for the delayed reply as I was on sick leave.
>> Sure. BTW, there are more such candidates which require 'lock' version
>> of these helpers.
>> For example: soc_find_component(), snd_soc_add/remove_pcm_runtime()
>> and snd_soc_register_dai().
> soc_find_component() is static function, no need to care about mutex.
> other functions are indeed exported function, but is used from
> topology.c which is calling it under mutex.
>
>
I was just thinking if we need to future proof these functions. As you
mentioned, currently these have limited usage (in topology.c) and should
just be fine to address snd_soc_find_dai() for now.
Thanks,
Sameer.
Powered by blists - more mailing lists