Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Shuming [范書銘]" <shumingf@realtek.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"lars@metafoo.de" <lars@metafoo.de>,
	"Flove(HsinFu)" <flove@realtek.com>,
	"Oder Chiou" <oder_chiou@realtek.com>,
	"Jack Yu" <jack.yu@realtek.com>,
	"Derek [方德義]" <derek.fang@realtek.com>,
	"Vijendar.Mukunda@amd.com" <Vijendar.Mukunda@amd.com>,
	"Bard Liao" <yung-chuan.liao@linux.intel.com>
Subject: Re: [PATCH 1/5] ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0
Date: Mon, 3 Jul 2023 14:25:07 +0200	[thread overview]
Message-ID: <a10894a2-a6af-8c5f-b675-79cc7cfeb899@linux.intel.com> (raw)
In-Reply-To: <81bf0fcc0b824c928e2e4e5a77ca37d8@realtek.com>



On 7/3/23 13:11, Shuming [范書銘] wrote:
>>> During ClockStop Mode0, peripheral interrupts are disabled.
>>
>> I can see that the interrupts are disabled in rt5682_dev_system_suspend(),
>> which is NOT a mode where the clock stop is used... I don't think this commit
>> message is correct.
>>
>> The IMPL_DEF interrupt which is used for jack detection is not disabled at all
>> during any clock stop mode, and it shouldn't otherwise that would break the
>> jack detection.
> 
> You are right. The commit message is wrong and not clear.
> The situation is that the manager driver uses the clock stop mode0 to do system suspension.

No it does not. The clock stop is ONLY used for pm_runtime, never for
system suspend. We cannot go to system suspend with the link in
clock-stop mode, that will create lots of issues, that's why we perform
a full pm_runtime resume in the .prepare stage.

> The SdW device will not be re-attached when the system resume.

it will re-attach, and in addition it will lose context because the
manager performs a complete reset of the bus.

So what's needed is to enable the interrupt, no matter what happened in
the suspend transition.


  reply	other threads:[~2023-07-03 12:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03  9:02 [PATCH 1/5] ASoC: rt5682-sdw: fix for JD event handling in ClockStop Mode0 shumingf
2023-07-03 10:17 ` Pierre-Louis Bossart
2023-07-03 11:11   ` Shuming [范書銘]
2023-07-03 12:25     ` Pierre-Louis Bossart [this message]
2023-07-03 13:00       ` Shuming [范書銘]
2023-07-03 13:31         ` Mukunda,Vijendar
2023-07-03 14:20           ` Pierre-Louis Bossart
2023-07-03 14:46             ` Mukunda,Vijendar
2023-07-03 14:45               ` Pierre-Louis Bossart
2023-07-03 15:18                 ` Mukunda,Vijendar
2023-07-03 17:18                   ` Pierre-Louis Bossart
2023-07-04  6:36                     ` Mukunda,Vijendar
2023-07-04  7:11                       ` Pierre-Louis Bossart
2023-07-04  7:37                         ` Mukunda,Vijendar
2023-07-04  8:27                           ` Pierre-Louis Bossart
2023-07-04  9:03                             ` Mukunda,Vijendar
2023-07-04  9:14                               ` 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=a10894a2-a6af-8c5f-b675-79cc7cfeb899@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=Vijendar.Mukunda@amd.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=derek.fang@realtek.com \
    --cc=flove@realtek.com \
    --cc=jack.yu@realtek.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=oder_chiou@realtek.com \
    --cc=shumingf@realtek.com \
    --cc=yung-chuan.liao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox