Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752514AbbEKG7C (ORCPT ); Mon, 11 May 2015 02:59:02 -0400 Received: from mail-ig0-f172.google.com ([209.85.213.172]:37009 "EHLO mail-ig0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752412AbbEKG67 (ORCPT ); Mon, 11 May 2015 02:58:59 -0400 MIME-Version: 1.0 In-Reply-To: <20150109174652.GE6575@google.com> References: <1417763857-11993-1-git-send-email-chuansheng.liu@intel.com> <20150109174652.GE6575@google.com> Date: Mon, 11 May 2015 14:58:58 +0800 X-Google-Sender-Auth: m5Q2cPxbN3G1Dmb9gUgd6SsKVDA Message-ID: Subject: Re: [PATCH] PCI: Add disabling pm async quirk for JMicron chips From: Aaron Lu To: Bjorn Helgaas Cc: Alan Stern , Chuansheng Liu , "Rafael J. Wysocki" , mister.freeman@laposte.net, Tejun Heo , Kernel development list , linux-pci@vger.kernel.org, Linux-pm mailing list , stable@vger.kernel.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1007 Lines: 26 On Sat, Jan 10, 2015 at 1:46 AM, Bjorn Helgaas wrote: > On Fri, Dec 05, 2014 at 02:18:40PM -0500, Alan Stern wrote: >> On Fri, 5 Dec 2014, Chuansheng Liu wrote: >> >> You know, this is exactly why device_pm_wait_for_dev() exists -- so >> that asynchronous power-management operations can wait for other >> devices even when there's no parent-child relation. >> >> You should try to use device_pm_wait_for_dev() instead of disabling >> async suspend/resume. > > Dropping this patch for now, waiting for a response to Alan's suggestion. >From Alan's comments #106: https://bugzilla.kernel.org/show_bug.cgi?id=81551#c106 It seems Chuansheng's patch is the best solution for now, so perhaps it can be considered to be merged? Regards, Aaron -- 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/