From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Harsha Priya <harshapriya.n@intel.com>,
Emmanuel Jillela <emmanuel.jillela@intel.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH v2] ALSA: HDA: Early Forbid of runtime PM
Date: Fri, 28 Aug 2020 18:03:38 +0300 (EEST) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2008281800180.3186@eliteleevi.tm.intel.com> (raw)
In-Reply-To: <s5h5z93ns23.wl-tiwai@suse.de>
Hey,
On Fri, 28 Aug 2020, Takashi Iwai wrote:
> On Fri, 28 Aug 2020 01:05:36 +0200, Harsha Priya wrote:
> > This issue being common across all codecs, pm_runtime_forbid() is
> > called when the codec object is created to fix this issue.
> > A codec enables or disables runtime pm in its own probe function.
>
> Thanks. The only concern is about the influence on the relevant ASoC
> code, especially hdac_hda.c.
>
> Kai, could you check whether this still works?
I believe Harsha is testing mostly with ASoC, so hdac_hda.c should be
covered.
I did queue a SOF CI job for this v2 patch and I'm seeing some failures
in module load/unload test that might be related and need checking before
we merge:
https://sof-ci.01.org/linuxpr/PR2403/build4400/devicetest/
The actual runtime-PM tests in our test set pass, but module load/unload
has failures on some platforms. I'll follow-up when I have a better
understanding what goes wrong.
Br, Kai
next prev parent reply other threads:[~2020-08-28 15:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-27 23:05 [PATCH v2] ALSA: HDA: Early Forbid of runtime PM Harsha Priya
2020-08-28 7:33 ` Takashi Iwai
2020-08-28 15:03 ` Kai Vehmanen [this message]
[not found] ` <BN6PR1101MB2275262388388F71D62390299C520@BN6PR1101MB2275.namprd11.prod.outlook.com>
2020-08-31 9:40 ` Takashi Iwai
2020-09-18 14:56 ` Kai Vehmanen
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=alpine.DEB.2.22.394.2008281800180.3186@eliteleevi.tm.intel.com \
--to=kai.vehmanen@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=emmanuel.jillela@intel.com \
--cc=harshapriya.n@intel.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).