All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@kernel.org>
Subject: Re: [alsa-devel] [PATCH 6/6] ASoC: soc-core: add snd_soc_stream_stop()
Date: 18 Dec 2019 10:51:41 +0900	[thread overview]
Message-ID: <87y2vajt8y.wl-kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <124fd50c-db99-7a4a-9e35-ad69b5e16abc@linux.intel.com>


Hi Pierre-Louis

> >> I noticed that soc_compr_free_fe(), dpcm_fe_dai_shutdown() are directly
> >> calling SND_SOC_DAPM_STREAM_STOP without caring pmdown time / delayed work.
> >> Can we use snd_soc_dapm_stream_stop() for these, too ?
> > 
> > That does seem like an oversight...
> 
> What would the rationale for deferring a FE shutdown though?
> 
> IIRC in the Intel machine drivers we only use .pm_ignore_downtime to
> backends to keep some clocks on, and even that is questionable (the
> clock dependencies should be properly modeled instead of hidden with
> an obscure dailink setting). When I asked why exactly this flag was
> set in most cases the reason why 'because others did so in the
> past'...

Not only "ignore_pmdown_time", but many flags are used
for such reasons, I guess...
But, it is "driver side setting issue", and same things happen
even if we have properly modeled clock dependencies, I guess unfortunately...

From framework side point of view, it should care settings anyway
if it was added/selected even though if it was added by copy-and-paste.
"Following settings case-by-case" is a little bit strange for me.
Maybe FE which has ignore_pmdown_time has some rationale, somehow ?

So, I will post v2 which renames function name that is pointed from you.
And, post additional patch which cares above +2 STREAM_STOP.
Feel free to post NACK it if you don't like it.
Then, Mark can just ignore it.

Thank you for your help !!
Best regards
---
Kuninori Morimoto
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-12-18  1:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-17  1:25 [alsa-devel] [PATCH 0/6] ASoC: soc-core cleanup step8 Kuninori Morimoto
2019-12-17  1:25 ` [alsa-devel] [PATCH 1/6] ASoC: soc-core: remove snd_soc_rtdcom_list Kuninori Morimoto
2019-12-17  1:25 ` [alsa-devel] [PATCH 2/6] ASoC: soc-core: care .ignore_suspend for Component suspend Kuninori Morimoto
2019-12-17  1:26 ` [alsa-devel] [PATCH 3/6] ASoC: soc-core: remove duplicate pinctrl operation when suspend Kuninori Morimoto
2019-12-17  1:26 ` [alsa-devel] [PATCH 4/6] ASoC: soc-core: do pinctrl_pm_select_xxx() as component Kuninori Morimoto
2019-12-17  1:26 ` [alsa-devel] [PATCH 5/6] ASoC: soc-core: add snd_soc_close_delayed_work() Kuninori Morimoto
2019-12-17  1:26 ` [alsa-devel] [PATCH 6/6] ASoC: soc-core: add snd_soc_stream_stop() Kuninori Morimoto
2019-12-17  3:22   ` Pierre-Louis Bossart
2019-12-17  3:54     ` Kuninori Morimoto
2019-12-17  4:41       ` Kuninori Morimoto
2019-12-17 12:13         ` Mark Brown
2019-12-17 13:56           ` Pierre-Louis Bossart
2019-12-18  1:51             ` Kuninori Morimoto [this message]
2019-12-18 11:50             ` 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=87y2vajt8y.wl-kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=pierre-louis.bossart@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 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.