From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: alsa-devel@alsa-project.org,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
ranjani.sridharan@linux.intel.com,
pierre-louis.bossart@linux.intel.com, broonie@kernel.org,
digetx@gmail.com
Subject: Re: [PATCH] ASoC: soc-pcm: Revert "call snd_soc_component_open/close() once"
Date: Tue, 3 Mar 2020 21:48:31 +0200 (EET) [thread overview]
Message-ID: <alpine.DEB.2.21.2003032107560.2957@eliteleevi.tm.intel.com> (raw)
In-Reply-To: <8736aq2rp2.wl-kuninori.morimoto.gx@renesas.com>
Hey,
On Tue, 3 Mar 2020, Kuninori Morimoto wrote:
> Kai Vehmanen wrote:
>> int snd_soc_component_close(struct snd_soc_component *component,
>> » » » struct snd_pcm_substream *substream)
>> {
>> /*
>> * lookup substream from "component->substream_List",
>> * only call driver->close() if found
>> */
>> ...
>>
>> ... this is arguably more code, but makes the state created in
>> snd_soc_component_open() explicit. Upon error in middle of
>
> But, 1 point I still not yet understand.
>
> close() will be called 1) when open failed, or, 2) normal close.
> If my understanding was correct, your code is caring that
> 2) normal close() might be called without open().
it also covers case (1) when open fails. So instead of the currently
merged error case rollback code in soc_pcm_components_open(), we'd just
call snd_pcm_components_close(substream) directly in case
of error. With tracking of opened substreams in soc-component.c, close()
is safe to call also in error case.
But you are right, I don't really see how (2) could be hit, so we are
essentially talking about how to avoid the <10 lines of rollback code in
soc_pcm_components_open(). :)
That considered, I'm fine if you can come up with a cleaner version to
handle just case (1), without tracking substreams. Maybe worth a try and
if it doesn't work (e.g. with ID/tag), we can look at substream tracking.
Br, Kai
next prev parent reply other threads:[~2020-03-03 19:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 18:26 [PATCH] ASoC: soc-pcm: Revert "call snd_soc_component_open/close() once" Kai Vehmanen
2020-02-19 18:53 ` Kai Vehmanen
2020-02-19 19:27 ` Pierre-Louis Bossart
2020-02-19 19:37 ` Dmitry Osipenko
2020-02-20 0:42 ` Kuninori Morimoto
2020-02-20 0:59 ` [PATCH][RFC] ASoC: soc-component: count snd_soc_component_open/close() Kuninori Morimoto
2020-02-20 1:25 ` Sridharan, Ranjani
2020-02-20 1:41 ` Kuninori Morimoto
2020-02-20 1:57 ` Sridharan, Ranjani
2020-02-20 3:01 ` Kuninori Morimoto
2020-02-20 9:33 ` [PATCH] ASoC: soc-pcm: Revert "call snd_soc_component_open/close() once" Kai Vehmanen
2020-02-21 1:13 ` Kuninori Morimoto
2020-02-21 11:09 ` Kai Vehmanen
2020-02-25 0:41 ` Kuninori Morimoto
2020-02-26 0:55 ` Kuninori Morimoto
2020-02-26 17:36 ` Mark Brown
2020-02-27 0:11 ` Kuninori Morimoto
2020-02-27 9:41 ` Kai Vehmanen
2020-02-28 0:46 ` Kuninori Morimoto
2020-02-28 6:27 ` Kuninori Morimoto
2020-02-28 7:57 ` Kuninori Morimoto
2020-02-28 12:23 ` Kai Vehmanen
2020-03-02 0:29 ` Kuninori Morimoto
2020-03-02 18:22 ` Kai Vehmanen
2020-03-03 0:43 ` Kuninori Morimoto
2020-03-03 19:48 ` Kai Vehmanen [this message]
2020-03-04 0:11 ` Kuninori Morimoto
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=alpine.DEB.2.21.2003032107560.2957@eliteleevi.tm.intel.com \
--to=kai.vehmanen@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=digetx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=pierre-louis.bossart@linux.intel.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;
as well as URLs for NNTP newsgroup(s).