From: Mark Brown <broonie@kernel.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org, Koro Chen <koro.chen@mediatek.com>,
Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: ASoC updates for v4.2
Date: Mon, 22 Jun 2015 11:30:34 +0100 [thread overview]
Message-ID: <20150622103034.GQ14071@sirena.org.uk> (raw)
In-Reply-To: <s5hmvzs6p4v.wl-tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 1000 bytes --]
On Mon, Jun 22, 2015 at 11:58:24AM +0200, Takashi Iwai wrote:
> In addition to rsnd-card.c, I get a compile warning as below:
> sound/soc/mediatek/mtk-afe-pcm.c:1035:12: warning: 'mtk_afe_runtime_suspend' defined but not used [-Wunused-function]
> And, looking at the code, it seems calling runtime suspend in the
> following way at probe:
> pm_runtime_enable(&pdev->dev);
> if (!pm_runtime_enabled(&pdev->dev)) {
> ret = mtk_afe_runtime_resume(&pdev->dev);
> if (ret)
> goto err_pm_disable;
> }
I'm confused, where's the call to runtime suspend?
> I'm not sure whether this really behaves correctly, especially when a
> kernel is built without CONFIG_PM.
Could you be more specific about the problem you're seeing? If runtime
PM is disabled pm_runtime_enabled() will return false and we'll run
through the resume path during probe() instead, otherwise we'll runtime
resume whenever we need to use the hardware.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-06-22 10:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 9:26 ASoC updates for v4.2 Mark Brown
2015-06-22 9:58 ` Takashi Iwai
2015-06-22 10:30 ` Mark Brown [this message]
2015-06-22 11:24 ` Takashi Iwai
2015-06-22 13:57 ` Mark Brown
2015-06-22 14:10 ` Takashi Iwai
2015-06-22 14:40 ` Takashi Iwai
2015-06-22 14:43 ` Mark Brown
2015-06-22 14:55 ` Takashi Iwai
2015-06-23 7:45 ` Koro Chen
2015-06-23 10:14 ` Mark Brown
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=20150622103034.GQ14071@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=koro.chen@mediatek.com \
--cc=lgirdwood@gmail.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