Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: HDA, power saving and recording
Date: Fri, 12 May 2023 13:23:49 +0200	[thread overview]
Message-ID: <87ilcxaj3u.wl-tiwai@suse.de> (raw)
In-Reply-To: <41417b90-1881-0cbb-52e1-d63923dd8cd6@linux.intel.com>

On Thu, 11 May 2023 19:20:17 +0200,
Amadeusz Sławiński wrote:
> 
> On 5/11/2023 5:58 PM, Takashi Iwai wrote:
> > On Thu, 11 May 2023 17:31:37 +0200,
> > Amadeusz Sławiński wrote:
> >> 
> >> On 5/10/2023 2:21 PM, Takashi Iwai wrote:
> >>> On Tue, 09 May 2023 12:10:06 +0200,
> >>> Amadeusz Sławiński wrote:
> >> Then capture stream starts and seems to assume that
> >> registers were already set, so it doesn't write them to hw.
> > 
> > ... it seems this didn't happen, and that's the inconsistency.
> > 
> > So the further question is:
> > At the point just before you start recording, is the codec in runtime
> > suspended?  Or it's running?
> > 
> > If it's runtime-suspended, snd_hda_regmap_sync() must be called from
> > alc269_resume() via runtime-resume, and this must write out the
> > cached values.  Then the bug can be along with that line.
> > 
> > Or if it's running, it means that the previous check of
> > snd_hdac_keep_power_up() was bogus (or racy).
> > 
> 
> Well, it is in... let's call it semi powered state. When snd_hda_intel
> driver is loaded with power_save=X option it sets timeout to X seconds
> and problem only happens when I start the stream before those X
> seconds pass and it runs first runtime suspend. After it suspends it
> then uses standard pm_runtime_resume and works correctly. That's why
> the pm_runtime_force_suspend(&codec->core.dev);  mentioned in first
> email in thread "fixes" the problem, as it forces it to be instantly
> suspended instead of waiting for timeout and then later normal
> resume-play/record-suspend flow can be followed.

Hm, then maybe it's a bad idea to rely on the usage count there.
Even if the usage is 0, the device can be still active, and the update
can be missed.

How about the patch like below?


thanks,

Takashi

--- a/sound/hda/hdac_device.c
+++ b/sound/hda/hdac_device.c
@@ -610,8 +610,12 @@ EXPORT_SYMBOL_GPL(snd_hdac_power_up_pm);
  */
 int snd_hdac_keep_power_up(struct hdac_device *codec)
 {
+	int ret;
+
 	if (!atomic_inc_not_zero(&codec->in_pm)) {
-		int ret = pm_runtime_get_if_in_use(&codec->dev);
+		if (pm_runtime_active(&codec->dev))
+			return pm_runtime_get_sync(&codec->dev);
+		ret = pm_runtime_get_if_in_use(&codec->dev);
 		if (!ret)
 			return -1;
 		if (ret < 0)

  reply	other threads:[~2023-05-12 11:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 10:10 HDA, power saving and recording Amadeusz Sławiński
2023-05-10 12:21 ` Takashi Iwai
2023-05-11 15:31   ` Amadeusz Sławiński
2023-05-11 15:58     ` Takashi Iwai
2023-05-11 17:20       ` Amadeusz Sławiński
2023-05-12 11:23         ` Takashi Iwai [this message]
2023-05-12 11:33           ` Takashi Iwai
2023-05-12 12:00             ` Amadeusz Sławiński
2023-05-12 12:24               ` Takashi Iwai
2023-05-15 11:19                 ` Amadeusz Sławiński
2023-05-15 13:02                   ` Takashi Iwai
2023-05-15 14:49                     ` Amadeusz Sławiński
2023-05-15 15:33                       ` Takashi Iwai
2023-05-17 13:15                         ` Cezary Rojewski
2023-05-17 14:52                           ` Takashi Iwai
2023-05-18  9:00                             ` Cezary Rojewski
2023-05-18 11:02                               ` Takashi Iwai

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=87ilcxaj3u.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=cezary.rojewski@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