Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935563AbZLPTUl (ORCPT ); Wed, 16 Dec 2009 14:20:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763153AbZLPTUd (ORCPT ); Wed, 16 Dec 2009 14:20:33 -0500 Received: from outbound-mail-120.bluehost.com ([69.89.18.6]:55682 "HELO outbound-mail-120.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1763146AbZLPTUO (ORCPT ); Wed, 16 Dec 2009 14:20:14 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=virtuousgeek.org; h=Received:Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:X-Mailer:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=e5cz+hHLDLV+X7ZicCNIz4hoM1peb+UwGTdGLYDI5cf7jVs/SwInlwbdz1BvNREktFaM2nrcB2i3eQye4z1bOQMdWiXhvFC1F70fJIkplg+ctNJ4beZ9gXUd9+hRM4Rh; Date: Wed, 16 Dec 2009 11:19:39 -0800 From: Jesse Barnes To: "Rafael J. Wysocki" Cc: pm list , LKML , Linux PCI , ACPI Devel Maling List , Alan Stern , Matthew Garrett , Oliver Neukum , Shaohua Li , Bjorn Helgaas , Francois Romieu , Len Brown Subject: Re: [RFC][PATCH 3/12] PCI / PM: Propagate wake-up enable for PCIe devices too Message-ID: <20091216111939.1a756377@jbarnes-piketon> In-Reply-To: <200911291635.54352.rjw@sisk.pl> References: <200911160047.46299.rjw@sisk.pl> <200911291632.44763.rjw@sisk.pl> <200911291635.54352.rjw@sisk.pl> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.18.3; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Identified-User: {10642:box514.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 75.111.28.251 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1146 Lines: 29 On Sun, 29 Nov 2009 16:35:54 +0100 "Rafael J. Wysocki" wrote: > From: Rafael J. Wysocki > > Having read the PM part of the PCIe 2.0 specification more carefully > I think that it was a mistake to restrict the wake-up enable > propagation to non-PCIe devices, because if we do not request > control of the root ports' PME registers via OSC, PCIe PME is > supposed to be handled by the platform, just like the non-PCIe PME. > Even if we do that, the wake-up propagation is done to allow the > devices to wake up the system from sleep states which involves the > platform anyway, so it won't hurt. > > Signed-off-by: Rafael J. Wysocki > --- > drivers/pci/pci-acpi.c | 10 ++-------- > 1 file changed, 2 insertions(+), 8 deletions(-) Applied after fixing up conflicts related to dev->is_pcie. Thanks, -- Jesse Barnes, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/