From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>,
alsa-devel@alsa-project.org, tiwai@suse.de,
Curtis Malainey <curtis@malainey.com>,
broonie@kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 1/5] ASoC: soc-link: introduce exit() callback
Date: Tue, 23 Jun 2020 09:50:29 -0500 [thread overview]
Message-ID: <5c020775-94db-0371-9a07-a1e59759a158@linux.intel.com> (raw)
In-Reply-To: <87imfi3bdd.wl-kuninori.morimoto.gx@renesas.com>
On 6/22/20 6:54 PM, Kuninori Morimoto wrote:
>
> Hi Pierre-Louis
>
>> The exit() is invoked in soc_remove_pcm_runtime(), which is not
>> completely symmetric with the init() invoked in soc_init_pcm_runtime().
> (snip)
>> @@ -945,6 +945,9 @@ void snd_soc_remove_pcm_runtime(struct snd_soc_card *card,
>> {
>> lockdep_assert_held(&client_mutex);
>>
>> + /* release machine specific resources */
>> + snd_soc_link_exit(rtd);
>
> I can understand that 100% symmetric calling init()/exit() is difficult.
> So we can't help it this time. But if so, it is easy to notice that
> this .exit() is the one of non-symmetric if it has such comment.
Sorry Morimoto-san, I don't understand your last sentence.
Were you suggesting to reword the "release machine specific resources"
comment above, or add a comment in the snd_soc_link_exit() definition,
or something else altogether?
I don't mind sending an update if you feel that makes the core more
readable.
Thanks!
next prev parent reply other threads:[~2020-06-23 15:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 15:42 [PATCH 0/5] ASoC: add dailink .exit() callback Pierre-Louis Bossart
2020-06-22 15:42 ` [PATCH 1/5] ASoC: soc-link: introduce exit() callback Pierre-Louis Bossart
2020-06-22 23:54 ` Kuninori Morimoto
2020-06-23 14:50 ` Pierre-Louis Bossart [this message]
2020-06-24 23:25 ` Kuninori Morimoto
2020-06-22 15:42 ` [PATCH 2/5] ASoC: Intel: bdw-rt5677: fix module load/unload issues Pierre-Louis Bossart
2020-06-22 18:18 ` Andy Shevchenko
2020-06-22 18:23 ` Pierre-Louis Bossart
2020-06-22 18:26 ` Mark Brown
2020-06-23 8:40 ` Andy Shevchenko
2020-06-23 9:37 ` Mark Brown
2020-06-23 8:43 ` Andy Shevchenko
2020-06-24 19:14 ` Cezary Rojewski
2020-06-24 20:06 ` Pierre-Louis Bossart
2020-06-24 20:26 ` Cezary Rojewski
2020-06-22 15:42 ` [PATCH 3/5] ASoC: Intel: kbl-rt5660: use .exit() dailink callback to release gpiod Pierre-Louis Bossart
2020-06-22 18:20 ` Andy Shevchenko
2020-06-22 18:26 ` Pierre-Louis Bossart
2020-06-23 8:39 ` Andy Shevchenko
2020-06-22 15:42 ` [PATCH 4/5] ASoC: intel: sof_rt5682: move disabling jack to dai link's exit() Pierre-Louis Bossart
2020-06-22 15:42 ` [PATCH 5/5] ASoC: intel: cml_rt1011_rt5682: disable jack in dailink .exit() Pierre-Louis Bossart
2020-06-23 12:39 ` [PATCH 0/5] ASoC: add dailink .exit() callback 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=5c020775-94db-0371-9a07-a1e59759a158@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=curtis@malainey.com \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.