From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Dmitry Osipenko <digetx@gmail.com>,
Mark Brown <broonie@kernel.org>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: alsa-devel@alsa-project.org, ranjani.sridharan@linux.intel.com,
kuninori.morimoto.gx@renesas.com
Subject: Re: [PATCH] ASoC: soc-pcm: fix state tracking error in snd_soc_component_open/close()
Date: Mon, 24 Feb 2020 11:05:33 -0600 [thread overview]
Message-ID: <59c8b078-f18f-1959-ccc7-b14674134daf@linux.intel.com> (raw)
In-Reply-To: <a435d244-573a-4e57-362d-08b7e4a6d012@gmail.com>
On 2/24/20 9:47 AM, Dmitry Osipenko wrote:
> 24.02.2020 15:01, Mark Brown пишет:
>> On Thu, Feb 20, 2020 at 11:49:55AM +0200, Kai Vehmanen wrote:
>>> ASoC component open/close and snd_soc_component_module_get/put are called
>>> independently for each component-substream pair, so the logic added in
>>> commit dd03907bf129 ("ASoC: soc-pcm: call snd_soc_component_open/close()
>>> once") was not sufficient and led to PCM playback and module unload errors.
>>>
>>> Implement handling of failures directly in soc_pcm_components_open(),
>>> so that any successfully opened components are closed upon error with
>>> other components. This allows to clean up error handling in
>>> soc_pcm_open() without adding more state tracking.
>>
>> Do people have thoughts on this? I do like this approach but can't
>> really test effectively myself.
>>
>
> I haven't tried to review this patch, but it works fine on NVIDIA Tegra:
>
> Tested-by: Dmitry Osipenko <digetx@gmail.com>
LGTM - I believe Kai tested for Intel platforms.
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Note that the code could be simplified further with a
for_each_rtd_components_rollback() macro, and we could also simplify the
hw_free code below - the use of the 'last' pointer is not really
necessary since we already have an index. That's for another cleanup though.
static int soc_pcm_components_hw_free(struct snd_pcm_substream *substream,
struct snd_soc_component *last)
{
struct snd_soc_pcm_runtime *rtd = substream->private_data;
struct snd_soc_component *component;
int i, r, ret = 0;
for_each_rtd_components(rtd, i, component) {
if (component == last)
break;
next prev parent reply other threads:[~2020-02-24 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 9:49 [PATCH] ASoC: soc-pcm: fix state tracking error in snd_soc_component_open/close() Kai Vehmanen
2020-02-24 12:01 ` Mark Brown
2020-02-24 15:47 ` Dmitry Osipenko
2020-02-24 17:05 ` Pierre-Louis Bossart [this message]
2020-02-24 22:21 ` Applied "ASoC: soc-pcm: fix state tracking error in snd_soc_component_open/close()" to the asoc tree Mark Brown
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=59c8b078-f18f-1959-ccc7-b14674134daf@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=digetx@gmail.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=ranjani.sridharan@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox