From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759128Ab3BWOtW (ORCPT ); Sat, 23 Feb 2013 09:49:22 -0500 Received: from mail-wg0-f50.google.com ([74.125.82.50]:59525 "EHLO mail-wg0-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759031Ab3BWOtT (ORCPT ); Sat, 23 Feb 2013 09:49:19 -0500 Date: Sat, 23 Feb 2013 15:48:59 +0100 From: Fabio Baltieri To: "Rafael J. Wysocki" Cc: Dave Jones , Greg KH , Linus Torvalds , Andrew Morton , linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, tianyu.lan@intel.com, linux-acpi@vger.kernel.org, Bjorn Helgaas , linux-pci@vger.kernel.org Subject: Re: [PATCH] ACPI / PM: Take unusual configurations of power resources into account (was: Re: [GIT PATCH] USB patches for 3.9-rc1) Message-ID: <20130223144859.GA2955@balto.lan> References: <20130222085954.GA4352@redhat.com> <1522889.3cbJt7lHsB@vostro.rjw.lan> <20130223114914.GA1786@balto.lan> <4258343.ok1n3SAim3@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4258343.ok1n3SAim3@vostro.rjw.lan> X-Operating-System: Linux balto 3.8.0-06544-g4f50cb1-dirty x86_64 GNU/Linux User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > From: Rafael J. Wysocki > Subject: ACPI / PM: Take unusual configurations of power resources into account > > Commit d2e5f0c (ACPI / PCI: Rework the setup and cleanup of device > wakeup) moved the initial disabling of system wakeup for PCI devices > into a place where it can actually work and that exposed a hidden old > issue with crap^Wunusual system designs where the same power > resources are used for both wakeup power and device power control at > run time. > > Namely, say there is one power resource such that the ACPI power > state D0 of a PCI device depends on that power resource (i.e. the > device is in D0 when that power resource is "on") and it is used > as a wakeup power resource for the same device. Then, calling > acpi_pci_sleep_wake(pci_dev, false) for the device in question will > cause the reference counter of that power resource to drop to 0, > which in turn will cause it to be turned off. As a result, the > device will go into D3cold at that point, although it should have > stayed in D0. > > As it turns out, that happens to USB controllers on some laptops > and USB becomes unusable on those machines as a result, which is > a major regression from v3.8. > > To fix this problem, (1) increment the reference counters of wakup > power resources during their initialization if they are "on" > initially, (2) prevent acpi_disable_wakeup_device_power() from > decrementing the reference counters of wakeup power resources that > were not enabled for wakeup power previously, and (3) prevent > acpi_enable_wakeup_device_power() from incrementing the reference > counters of wakeup power resources that already are enabled for > wakeup power. > > In addition to that, if it is impossible to determine the initial > states of wakeup power resources, avoid enabling wakeup for devices > whose wakeup power depends on those power resources. > > Reported-by: Dave Jones > Reported-by: Fabio Baltieri > Signed-off-by: Rafael J. Wysocki Works just fine! Tested-by: Fabio Baltieri Thanks, Fabio -- Fabio Baltieri