All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.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: Mon, 30 Mar 2020 18:49:30 -0500	[thread overview]
Message-ID: <cfb3612e-e453-526d-8351-9167f26fecca@linux.intel.com> (raw)
In-Reply-To: <259cbb60-9e59-1132-8371-83f837577f86@redhat.com>


>> Btw the .ignore_suspend is also set in bytcr_rt5640/51 drivers, so 
>> wondering if additional devices are broken, or if there's something 
>> off about Broadwell in general. Hans, have you heard of any 
>> regressions on Baytrail devices?
> 
> I've just tested 5.6.0 on Bay Trail + a rt5651 codec,
> using the bytcr_rt5651 machine driver which sets
> ignore_suspend, as well as on a Cherry Trail + rt5645
> device using the chtrt5645 machine driver which does
> _not_ set ignore suspend.
> 
> Suspend/resume work fine on both and music playing
> before suspend continues playing after suspend.

Thanks for testing Hans.

I think we should remove those .ignore_suspend from all 
Baytrail/Cherrytrail drivers, no one ever enabled advanced power 
management except in very specific Android distributions that are no 
longer maintained.
> 
> Note that the bytcr_rt5651 machine driver also does:
> 
>          snd_soc_dapm_ignore_suspend(&card->dapm, "Headphone");
>          snd_soc_dapm_ignore_suspend(&card->dapm, "Speaker");
> 
> Which the bdw-rt5677 seems to not do...


On the bytcr_rt5661, these two lines were added in the initial code in 
2016, and it's also part of the legacy byt-rt5640, so it's likely a 
copy/paste more than a feature added on purpose.

  reply	other threads:[~2020-03-31 12:38 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 [this message]
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
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=cfb3612e-e453-526d-8351-9167f26fecca@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.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=hdegoede@redhat.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux@dominikbrodowski.net \
    --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.