All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Cezary Rojewski <cezary.rojewski@intel.com>,
	alsa-devel@alsa-project.org
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Curtis Malainey <cujomalainey@google.com>,
	tiwai@suse.com, Dominik Brodowski <linux@dominikbrodowski.net>,
	lgirdwood@gmail.com, vkoul@kernel.org, broonie@kernel.org,
	Ben Zhang <benzh@google.com>
Subject: Re: [PATCH 3/4] ASoC: Intel: bdw-rt5677: Remove ignore_suspend flag from SSP0 dai link
Date: Tue, 31 Mar 2020 14:12:51 +0200	[thread overview]
Message-ID: <62061e77-e855-e4e0-1e5d-8d9ccd422011@redhat.com> (raw)
In-Reply-To: <a48d48cb-ab02-1213-88b9-431109e4b468@linux.intel.com>

Hi,

On 3/31/20 12:54 PM, Pierre-Louis Bossart wrote:
> 
>> Don't believe WoV for WPT has been added for SST linux so .ignore_suspend=1 achieves nothing. The offload part is probably just limited to bigger buffer size compared to system pin than anything else. So, nothing prevents from removing .ignore_suspend for SST solutions until WoV is verified. Don't know about SOF side.
>> Pierre, what's your take on this?
> 
> I think on Baytrail and Broadwell we will most likely never enable hotwording on the Intel DSP, and S0i1-Playback isn't planned either.
> 
> However hotwording is enabled on the RT5677 and there may be clocking dependencies so that the RT5677 remains operational - at least the mclk needs to be on, so the bdw-rt5677 case probably needs more work.
> 
> While I am at it, I think the notion of .ignore_suspend has an assumption baked in. It will work if the only suspend mode is S0i1. If the platform can choose between S0i1 and S3, then we would still want to suspend all paths in S3, which currently isn't really possible.

You can check if S0i1 will be used by using:

pm_suspend_default_s2idle()

If this returns true then S0i1 will be used, otherwise S3.

This is defined in kernel/power/suspend.c and always build, so it
should be ok to also use this in non x86 specific code-paths
(it will simply always return false there I believe).

Regards,

Hans


  reply	other threads:[~2020-03-31 12:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 20:49 [PATCH 0/4] ASoC: Intel: boards: Remove ignore_suspend flag from SSP0 dai link Cezary Rojewski
2020-03-19 20:49 ` [PATCH 1/4] ASoC: Intel: broadwell: " Cezary Rojewski
2020-03-30 17:23   ` Applied "ASoC: Intel: broadwell: Remove ignore_suspend flag from SSP0 dai link" to the asoc tree Mark Brown
2020-03-19 20:49 ` [PATCH 2/4] ASoC: Intel: haswell: Remove ignore_suspend flag from SSP0 dai link Cezary Rojewski
2020-03-30 17:23   ` Applied "ASoC: Intel: haswell: Remove ignore_suspend flag from SSP0 dai link" to the asoc tree Mark Brown
2020-03-19 20:49 ` [PATCH 3/4] ASoC: Intel: bdw-rt5677: Remove ignore_suspend flag from SSP0 dai link Cezary Rojewski
2020-03-19 22:14   ` Pierre-Louis Bossart
2020-03-19 22:43     ` Curtis Malainey
2020-03-25 13:28       ` Cezary Rojewski
2020-03-25 14:42         ` Pierre-Louis Bossart
2020-03-30 21:39     ` Hans de Goede
2020-03-30 23:49       ` Pierre-Louis Bossart
2020-03-31 12:15         ` Hans de Goede
2020-03-31 10:28       ` Cezary Rojewski
2020-03-31 10:54         ` Pierre-Louis Bossart
2020-03-31 12:12           ` Hans de Goede [this message]
2020-03-31 12:15             ` Pierre-Louis Bossart
2020-04-05 18:10       ` Hans de Goede
2020-04-05 23:11         ` Pierre-Louis Bossart
2020-03-30 17:23   ` Applied "ASoC: Intel: bdw-rt5677: Remove ignore_suspend flag from SSP0 dai link" to the asoc tree Mark Brown
2020-03-19 20:49 ` [PATCH 4/4] ASoC: Intel: bdw-rt5650: Remove ignore_suspend flag from SSP0 dai link Cezary Rojewski
2020-03-30 17:23   ` Applied "ASoC: Intel: bdw-rt5650: Remove ignore_suspend flag from SSP0 dai link" to the asoc tree Mark Brown
2020-03-30 15:40 ` [PATCH 0/4] ASoC: Intel: boards: Remove ignore_suspend flag from SSP0 dai link Pierre-Louis Bossart

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=62061e77-e855-e4e0-1e5d-8d9ccd422011@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=benzh@google.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=cujomalainey@google.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux@dominikbrodowski.net \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=tiwai@suse.com \
    --cc=vkoul@kernel.org \
    /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.