All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: alsa-devel@alsa-project.org, Linux PM <linux-pm@vger.kernel.org>
Subject: Re: Warning due to "ALSA: hda: intel: More comprehensive PM runtime setup for controller driver"
Date: Thu, 18 Nov 2021 22:28:21 +0100	[thread overview]
Message-ID: <s5hczmxgnm2.wl-tiwai@suse.de> (raw)
In-Reply-To: <d9d76980-966a-e031-70d1-3254ba5be5eb@gmail.com>

On Thu, 18 Nov 2021 21:33:34 +0100,
Heiner Kallweit wrote:
> 
> I get the following warning caused by 4f66a9ef37d3 ("ALSA: hda: intel: More
> comprehensive PM runtime setup for controller driver"):
> 
> snd_hda_intel 0000:00:1f.3: Unbalanced pm_runtime_enable!
> 
> Not sure how this patch was tested because the warning is obvious.
> The patch doesn't consider what the PCI sub-system does with regard to
> RPM. Have a look at pci_pm_init().
> 
> I'd understand to add the call to pm_runtime_dont_use_autosuspend(),
> but for all other added calls I see no justification.
> 
> If being unsure about when to use which RPM call best involve
> linux-pm@vger.kernel.org.

Thanks for the notice.  It's been through Intel CI and tests on a few
local machines, maybe we haven't checked carefully those errors but
only concentrated on the other issues, as it seems.

There were two problems: one was the runtime PM being kicked off even
during the PCI driver remove call, and another was the proper runtime
PM setup after re-binding.

For avoiding the former, only the pm_runtime_forbid() (and maybe
pm_runtime_dont_use_autosuspend(), too) would suffice?  Also, for PCI
device, no need for pm_runtime_set_supended() at remove, right?


thanks,

Takashi

  reply	other threads:[~2021-11-18 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 20:33 Warning due to "ALSA: hda: intel: More comprehensive PM runtime setup for controller driver" Heiner Kallweit
2021-11-18 21:28 ` Takashi Iwai [this message]
2021-11-18 22:13   ` Heiner Kallweit
2021-11-19 13:51     ` Takashi Iwai
2021-11-19 15:10       ` Kai Vehmanen
2021-11-19 15:10         ` Kai Vehmanen
2021-11-19 20:57       ` Heiner Kallweit

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=s5hczmxgnm2.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=hkallweit1@gmail.com \
    --cc=linux-pm@vger.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.