linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Lin Ming <ming.m.lin@intel.com>
Cc: "Yan, Zheng" <zheng.z.yan@intel.com>,
	bhelgaas@google.com, linux-kernel@vger.kernel.org,
	linux-pci@vger.kernel.org, linux-pm@vger.kernel.org,
	Zhang Rui <rui.zhang@intel.com>,
	huang ying <huang.ying.caritas@gmail.com>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: [RFC PATCH] PCIe: Add PCIe runtime D3cold support
Date: Mon, 16 Apr 2012 18:26:51 +0200	[thread overview]
Message-ID: <201204161826.51743.rjw@sisk.pl> (raw)
In-Reply-To: <1334537311.11188.118.camel@minggr>

On Monday, April 16, 2012, Lin Ming wrote:
> On Fri, 2012-04-13 at 21:41 +0200, Rafael J. Wysocki wrote:
> > Hi,
> > 
> > On Friday, April 13, 2012, Yan, Zheng wrote:
> > > Hi all,
> > > 
> > > This patch adds PCIe runtime D3cold support, namely cut power supply for functions
> > > beneath a PCIe port when they all have entered D3. A device in D3cold can only
> > > generate wake event through the WAKE# pin. Because we can not access to a device's
> > > configure space while it's in D3cold, pme_poll is disabled for devices in D3cold.
> > > 
> > > Any comment will be appreciated.
> > > 
> > > Signed-off-by: Zheng Yan <zheng.z.yan@intel.com>
> > > ---
> > > diff --git a/drivers/pci/pci-acpi.c b/drivers/pci/pci-acpi.c
> > > index 0f150f2..e210e8cb 100644
> > > --- a/drivers/pci/pci-acpi.c
> > > +++ b/drivers/pci/pci-acpi.c
> > > @@ -224,7 +224,7 @@ static int acpi_pci_set_power_state(struct pci_dev *dev, pci_power_t state)
> > >  		[PCI_D1] = ACPI_STATE_D1,
> > >  		[PCI_D2] = ACPI_STATE_D2,
> > >  		[PCI_D3hot] = ACPI_STATE_D3,
> > > -		[PCI_D3cold] = ACPI_STATE_D3
> > > +		[PCI_D3cold] = ACPI_STATE_D3_COLD
> > >  	};
> > >  	int error = -EINVAL;
> > >  
> > 
> > Please don't use that ACPI_STATE_D3_COLD thing, it's not defined correctly.
> > 
> > We should define ACPI_STATE_D3_COLD == ACPI_STATE_D3 and add ACPI_STATE_D3_HOT
> > instead.  I'll prepare a patch for that over the weekend if no one has done
> > that already.
> 
> Hi Rafael,
> 
> Have you started to write the patch?
> 
> If not, I can do it.

Please do if you have the time.  I'd like this one to be cleaned up ASAP,
to reduce the amount of confusion taking place.

Thanks,
Rafael

  reply	other threads:[~2012-04-16 16:26 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13  2:35 [RFC PATCH] PCIe: Add PCIe runtime D3cold support Yan, Zheng
2012-04-13  6:06 ` Alex He
2012-04-13  6:28   ` Yan, Zheng
2012-04-16  8:15   ` huang ying
2012-04-13 19:41 ` Rafael J. Wysocki
2012-04-16  0:48   ` Lin Ming
2012-04-16 16:26     ` Rafael J. Wysocki [this message]
2012-04-16  2:23   ` Yan, Zheng
2012-04-16 17:07     ` Rafael J. Wysocki
2012-04-17  2:07       ` huang ying
2012-04-17 20:20         ` Rafael J. Wysocki
2012-04-18  1:19           ` huang ying
2012-04-18 19:51             ` Rafael J. Wysocki
2012-04-17  2:12       ` Yan, Zheng
2012-04-17  5:32         ` huang ying
2012-04-17 20:43           ` Rafael J. Wysocki
2012-04-18  1:22             ` huang ying
2012-04-18 19:52               ` Rafael J. Wysocki
2012-04-17 20:35         ` Rafael J. Wysocki
2012-04-16  7:49   ` Yan, Zheng
2012-04-16 21:11     ` Rafael J. Wysocki
2012-04-16  8:58   ` huang ying
2012-04-16 21:30     ` Rafael J. Wysocki
2012-04-17  2:02       ` huang ying
2012-04-17 21:03         ` Rafael J. Wysocki
2012-04-18  1:45           ` huang ying
2012-04-18 21:00             ` Rafael J. Wysocki
2012-04-19  2:47               ` huang ying
2012-04-19 12:31                 ` Rafael J. Wysocki
2012-04-20  0:48                   ` huang ying
2012-04-17  5:13       ` huang ying
2012-04-17 21:10         ` Rafael J. Wysocki
2012-04-18  2:01           ` huang ying
2012-04-18 20:51             ` Rafael J. Wysocki
2012-04-19  2:08               ` huang ying
2012-04-19 12:36                 ` Rafael J. Wysocki
2012-04-20  0:53                   ` huang ying

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=201204161826.51743.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=bhelgaas@google.com \
    --cc=huang.ying.caritas@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=rui.zhang@intel.com \
    --cc=zheng.z.yan@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;
as well as URLs for NNTP newsgroup(s).