From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
"Sridharan, Ranjani" <ranjani.sridharan@intel.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Subject: Re: [alsa-devel] [PATCH v2 2/7] ASoC: soc-core: care .ignore_suspend for Component suspend
Date: Wed, 18 Dec 2019 11:48:18 -0600 [thread overview]
Message-ID: <aa512532-908d-c1e4-6284-b550da05d3f2@linux.intel.com> (raw)
In-Reply-To: <20191218171415.GJ3219@sirena.org.uk>
On 12/18/19 11:14 AM, Mark Brown wrote:
> On Wed, Dec 18, 2019 at 08:54:27AM -0600, Pierre-Louis Bossart wrote:
>
>> Even for dai links, it's not clear to me what .ignore_suspend means.
>
> It means exactly what it says, don't do anything on suspend.
>
>> For Intel machine drivers, the .ignore_suspend flag is used for DMIC links
>> which may be used in S0ix/D0ix states. I don't believe this works if there
>> are multiple target states, e.g. you would probably want to leave the link
>> active in S0ix, but suspend it in S3?
>
>> I think the current .ignore_suspend settings only work with the assumption
>> that applications will close all capture streams before going to S3.
>
> These numbered suspend states are a platform specific concept, other
> systems will typically just suspend or not suspend. It sounds like this
> feature does not map onto your systems.
Correct. What is not clear to me is how we can specify a behavior that
would be dependent on the target states.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-12-18 18:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 2:44 [alsa-devel] [PATCH 0/7 v2] ASoC: soc-core cleanup step8 Kuninori Morimoto
2019-12-18 2:45 ` [alsa-devel] [PATCH v2 1/7] ASoC: soc-core: remove snd_soc_rtdcom_list Kuninori Morimoto
2019-12-18 3:31 ` Sridharan, Ranjani
2019-12-18 3:53 ` Kuninori Morimoto
2019-12-18 2:45 ` [alsa-devel] [PATCH v2 2/7] ASoC: soc-core: care .ignore_suspend for Component suspend Kuninori Morimoto
2019-12-18 3:36 ` Sridharan, Ranjani
2019-12-18 3:59 ` Kuninori Morimoto
2019-12-18 14:54 ` Pierre-Louis Bossart
2019-12-18 17:14 ` Mark Brown
2019-12-18 17:48 ` Pierre-Louis Bossart [this message]
2019-12-18 18:06 ` Mark Brown
2019-12-18 2:45 ` [alsa-devel] [PATCH v2 3/7] ASoC: soc-core: remove duplicate pinctrl operation when suspend Kuninori Morimoto
2019-12-18 2:46 ` [alsa-devel] [PATCH v2 4/7] ASoC: soc-core: do pinctrl_pm_select_xxx() as component Kuninori Morimoto
2019-12-18 2:46 ` [alsa-devel] [PATCH v2 5/7] ASoC: soc-core: add snd_soc_close_delayed_work() Kuninori Morimoto
2019-12-18 2:47 ` [alsa-devel] [PATCH v2 6/7] ASoC: soc-dapm: add snd_soc_dapm_stream_stop() Kuninori Morimoto
2019-12-18 2:47 ` [alsa-devel] [PATCH v2 7/7] ASoC: use snd_soc_dapm_stream_stop() for SND_SOC_DAPM_STREAM_STOP Kuninori Morimoto
2019-12-18 6:06 ` [alsa-devel] [PATCH 0/7 v2] ASoC: soc-core cleanup step8 Ranjani Sridharan
2019-12-19 5:57 ` 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=aa512532-908d-c1e4-6284-b550da05d3f2@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=ranjani.sridharan@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