From: Takashi Iwai <tiwai@suse.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: alsa-devel@alsa-project.org, jocelyn.li@intel.com,
intel-gfx@lists.freedesktop.org,
Wang Xingchao <xingchao.wang@linux.intel.com>,
liam.r.girdwood@intel.com
Subject: Re: [alsa-devel] [PATCH 3/4] ALSA: hda - Fix runtime PM check
Date: Thu, 23 May 2013 14:39:36 +0200 [thread overview]
Message-ID: <s5hehcxx43b.wl%tiwai@suse.de> (raw)
In-Reply-To: <519E0CC1.4070300@canonical.com>
At Thu, 23 May 2013 14:34:09 +0200,
David Henningsson wrote:
>
> On 05/22/2013 07:04 PM, Wang Xingchao wrote:
> > The device can support runtime PM no matter whether
> > it support signal wakeup or not. For some chips like Haswell
> > which doesnot support PME by default, this patch let haswell
> > Display HD-A controller enter runtime suspend, and bring more
> > power saving whith power-well feature enabled.
> > Signed-off-by: Wang Xingchao <xingchao.wang@linux.intel.com>
> > ---
> > sound/pci/hda/hda_intel.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c
> > index 54c7c22..f20a88c 100644
> > --- a/sound/pci/hda/hda_intel.c
> > +++ b/sound/pci/hda/hda_intel.c
> > @@ -3755,7 +3755,7 @@ static int azx_probe(struct pci_dev *pci,
> > goto out_free_power;
> > }
> >
> > - if (pci_dev_run_wake(pci))
> > + if (chip->driver_caps & AZX_DCAPS_PM_RUNTIME)
>
> I'm not sure, but shouldn't this be
>
> if (pci_dev_run_wake(pci) || (chip->driver_caps & AZX_DCAPS_PM_RUNTIME))
>
> ...in order not to regress power performance of devices which have
> pci_dev_run_wake(pci) but not runtime PM?
If driver_caps isn't set, azx_runtime_idle() returns -EBUSY,
i.e. essentially the runtime PM is disabled in that case.
Takashi
> > pm_runtime_put_noidle(&pci->dev);
> >
> > dev++;
> > @@ -3834,7 +3834,7 @@ static void azx_remove(struct pci_dev *pci)
> > struct snd_card *card = pci_get_drvdata(pci);
> > struct azx *chip = card->private_data;
> >
> > - if (pci_dev_run_wake(pci))
> > + if (chip->driver_caps & AZX_DCAPS_PM_RUNTIME)
> > pm_runtime_get_noresume(&pci->dev);
> >
> > if (card)
> >
>
>
>
> --
> David Henningsson, Canonical Ltd.
> https://launchpad.net/~diwic
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2013-05-23 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 17:04 [PATCH 0/4 V5] Power-well API implementation for Haswell Wang Xingchao
2013-05-22 17:04 ` [PATCH 1/4 V5] i915/drm: Add private api for power well usage Wang Xingchao
2013-05-23 15:14 ` Takashi Iwai
2013-05-22 17:04 ` [PATCH 2/4 V5] ALSA: hda - Add power-welll support for haswell HDA Wang Xingchao
2013-05-22 17:04 ` [PATCH 3/4] ALSA: hda - Fix runtime PM check Wang Xingchao
2013-05-23 6:02 ` Takashi Iwai
2013-05-23 7:53 ` Wang, Xingchao
2013-05-23 8:09 ` Takashi Iwai
2013-05-23 10:20 ` Wang, Xingchao
2013-05-23 12:34 ` David Henningsson
2013-05-23 12:39 ` Takashi Iwai [this message]
2013-05-22 17:04 ` [PATCH 4/4] ALSA: hda - Continue probe in work context to avoid request_module deadlock Wang Xingchao
2013-05-23 6:47 ` 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=s5hehcxx43b.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jocelyn.li@intel.com \
--cc=liam.r.girdwood@intel.com \
--cc=xingchao.wang@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