alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: bhelgaas@google.com, alsa-devel@alsa-project.org,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/2] PCI: Add a helper to check Power Resource Requirements _PR3 existence
Date: Tue, 27 Aug 2019 17:25:10 +0200	[thread overview]
Message-ID: <s5hr2567hrd.wl-tiwai@suse.de> (raw)
In-Reply-To: <20190827134756.10807-1-kai.heng.feng@canonical.com>

On Tue, 27 Aug 2019 15:47:55 +0200,
Kai-Heng Feng wrote:
> 
> A driver may want to know the existence of _PR3, to choose different
> runtime suspend behavior. A user will be add in next patch.
> 
> This is mostly the same as nouveau_pr3_present().

Then it'd be nice to clean up the nouveau part, too?


thanks,

Takashi

  parent reply	other threads:[~2019-08-27 15:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 13:47 [PATCH 1/2] PCI: Add a helper to check Power Resource Requirements _PR3 existence Kai-Heng Feng
2019-08-27 13:47 ` [PATCH 2/2] ALSA: hda: Allow HDA to be runtime suspended when dGPU is not bound Kai-Heng Feng
2019-08-27 14:50   ` Kai-Heng Feng
2019-08-27 15:24   ` Takashi Iwai
2019-08-27 22:31   ` Bjorn Helgaas
2019-08-28  8:25     ` Kai-Heng Feng
2019-08-28 18:01   ` [PATCH v2 " Kai-Heng Feng
2019-09-05 21:35     ` [alsa-devel] " Bjorn Helgaas
2019-09-17  9:36       ` Kai-Heng Feng
2019-09-18 12:42     ` [alsa-devel] [PATCH v3 2/2] ALSA: hda: Allow HDA to be runtime suspended when dGPU is not bound to a driver Kai-Heng Feng
2019-08-27 15:25 ` Takashi Iwai [this message]
2019-08-27 16:58   ` [PATCH 1/2] PCI: Add a helper to check Power Resource Requirements _PR3 existence Kai-Heng Feng
2019-08-27 22:13     ` Bjorn Helgaas
2019-08-27 22:39       ` Peter Wu
2019-09-09 11:41 ` [alsa-devel] " Bjorn Helgaas
2019-09-20 11:23   ` Kai-Heng Feng
2019-09-20 13:26     ` Bjorn Helgaas

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=s5hr2567hrd.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=bhelgaas@google.com \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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 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).