From: Takashi Iwai <tiwai@suse.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: alsa-devel@alsa-project.org, intel-gfx@lists.freedesktop.org
Subject: Re: snd-hda-intel runtime PM fail after module reload
Date: Thu, 25 Feb 2016 21:28:59 +0100 [thread overview]
Message-ID: <s5hwppsy1o4.wl-tiwai@suse.de> (raw)
In-Reply-To: <20160225191908.GN15993@intel.com>
On Thu, 25 Feb 2016 20:19:08 +0100,
Ville Syrjälä wrote:
>
> Hi,
>
> My investigation into some sporadic i915 runtime PM failures seem to
> point the finger at snd-hda-intel.
>
> I just tried to play around unloding and reloading snd-hda-intel and
> sometimes I get snd-hda-intel loaded with runtime PM supposedly enabled,
> but actually the device won't runtime suspend. At which point frobbing
> with power/control is enough to kick it back into submission.
Which platform are you testing? If it's SKL, BSW or later, multiple
codecs are on a single HD-audio bus. In general, you have to adjust
the runtime PM of all these codecs in addition to the runtime PM of
the controller. Some of them are immediately runtime PM enabled but
some of them aren't, left the default as is.
It might be that your desktop environment adjusts the runtime PM of
HD-audio stuff, often depending on the power state. But when you
reload, this adjustment is also lost, so you'd have to adjust
manually.
Takashi
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-25 20:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 19:19 snd-hda-intel runtime PM fail after module reload Ville Syrjälä
2016-02-25 20:28 ` Takashi Iwai [this message]
2016-02-25 21:57 ` Ville Syrjälä
2016-02-26 7:49 ` 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=s5hwppsy1o4.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@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