From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Paul Stewart <pstew@google.com>
Cc: "Luis R. Rodriguez" <lrodriguez@atheros.com>,
LKML <linux-kernel@vger.kernel.org>,
"Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>,
linux-wireless@vger.kernel.org, ath9k-devel@venema.h4ckr.net
Subject: Re: [PATCH] ath9k: Convert to new PCI PM framework
Date: Sat, 16 Oct 2010 21:52:24 +0200 [thread overview]
Message-ID: <201010162152.24344.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTimXXERRCYEjzQbcii6XW8wbjNfN-eWigU7Wi_Lv@mail.gmail.com>
On Saturday, October 16, 2010, Paul Stewart wrote:
> On Fri, Oct 15, 2010 at 3:36 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > From: Rafael J. Wysocki <rjw@sisk.pl>
> >
> > 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
next prev parent reply other threads:[~2010-10-16 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 22:36 [PATCH] ath9k: Convert to new PCI PM framework Rafael J. Wysocki
2010-10-15 23:54 ` Luis R. Rodriguez
2010-10-16 20:02 ` Rafael J. Wysocki
2010-10-16 1:28 ` Paul Stewart
2010-10-16 19:52 ` Rafael J. Wysocki [this message]
2010-12-19 23:32 ` [PATCH] ath9k: Do not use legacy PCI power management Rafael J. Wysocki
2010-12-20 0:05 ` Hauke Mehrtens
2010-12-20 0:14 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201010162152.24344.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
--cc=pstew@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox