Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:52671 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754149Ab0JPTxW (ORCPT ); Sat, 16 Oct 2010 15:53:22 -0400 From: "Rafael J. Wysocki" To: Paul Stewart Subject: Re: [PATCH] ath9k: Convert to new PCI PM framework Date: Sat, 16 Oct 2010 21:52:24 +0200 Cc: "Luis R. Rodriguez" , LKML , "Linux-pm mailing list" , linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net References: <201010160036.17653.rjw@sisk.pl> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Message-Id: <201010162152.24344.rjw@sisk.pl> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Saturday, October 16, 2010, Paul Stewart wrote: > On Fri, Oct 15, 2010 at 3:36 PM, Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > The ath9k driver uses the legacy PCI power management (suspend > > and resume) callbacks that apparently cause intermittent problems > > to happen (the adapter sometimes doesn't resume correctly on my > > Acer Ferrari One). Make it use the new PCI PM and let the PCI core > > code handle the PCI-specific details of power transitions. > I'm curious. What sort of behavior did you get when the device fails > to resume correctly? Every now and then I've been getting bad > accesses to 0x7000 every now and then -- after that any reads to PCI > registers return all f's. Yes, this sort of matches my experience. Even the config space isn't really accessible after a failure to resume. Thanks, Rafael