Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751169Ab2KGFa7 (ORCPT ); Wed, 7 Nov 2012 00:30:59 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55936 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750747Ab2KGFa6 (ORCPT ); Wed, 7 Nov 2012 00:30:58 -0500 From: Dave Airlie To: linux-pci@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Dave Airlie , Huang Ying , Bjorn Helgaas , "Rafael J. Wysocki" Subject: [PATCH] pci/runtime-pm: respect devices autosuspend timeout on config access Date: Wed, 7 Nov 2012 15:30:09 +1000 Message-Id: <1352266209-29796-1-git-send-email-airlied@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1290 Lines: 36 So I've been adding runtime pm to nouveau/radeon, and on X start it does a lot of pci accesses. Now because the pm on these devices is equivalent to D3cold, we have to resume them which involves a heavy latency due to POSTing the cards. The driver configures the autosuspend timeout to 5s for this reason, and I think the PCI layer config accesses should respect the autosuspend. Cc: Huang Ying Cc: Bjorn Helgaas Cc: Rafael J. Wysocki Signed-off-by: Dave Airlie --- drivers/pci/pci-sysfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pci/pci-sysfs.c b/drivers/pci/pci-sysfs.c index 02d107b..12d3d52 100644 --- a/drivers/pci/pci-sysfs.c +++ b/drivers/pci/pci-sysfs.c @@ -487,7 +487,7 @@ pci_config_pm_runtime_put(struct pci_dev *pdev) struct device *dev = &pdev->dev; struct device *parent = dev->parent; - pm_runtime_put(dev); + pm_runtime_put_autosuspend(dev); if (parent) pm_runtime_put_sync(parent); } -- 1.7.12.1 -- 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/