From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Greg KH <gregkh@suse.de>
Cc: Pavel Machek <pavel@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
trenn@suse.de, thoenig@suse.de
Subject: Re: [RFC] [PATCH] Execute PCI quirks on resume from suspend-to-RAM
Date: Wed, 10 May 2006 23:36:41 +0200 [thread overview]
Message-ID: <44625CE9.2060204@gmx.net> (raw)
In-Reply-To: <20060510205600.GB23446@suse.de>
Greg KH wrote:
> On Wed, May 10, 2006 at 12:30:34PM +0200, Carl-Daniel Hailfinger wrote:
>> Thinking about it again, if we restored the full pci config space
>> on resume, this quirk handling would be completely unnecessary.
>> Any reasons why we don't do that?
>
> We do do that. Look at pci_restore_state().
>
> Actually, look at it in the latest -mm tree, that version works better
> than mainline does right now :)
Sorry. Even the version in -mm does not restore all 256 bytes, so it
will not change anything. The quirk sits at offset 0xf2 in config space.
So either we really restore the full config space (probably a good idea
by itself) or we add the quirk handling to the suspend-to-ram codepath.
On a related note, what happens if we try to restore the config space of
a device which has vanished? Right now this happens on all mainboards
with asus_hides_smbus==1 during resume-from-ram.
Greg, do you have any comments on the patch starting this thread?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2006-05-10 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 0:55 [RFC] [PATCH] Execute PCI quirks on resume from suspend-to-RAM Carl-Daniel Hailfinger
2006-05-10 9:39 ` Pavel Machek
2006-05-10 10:30 ` Carl-Daniel Hailfinger
2006-05-10 20:56 ` Greg KH
2006-05-10 21:36 ` Carl-Daniel Hailfinger [this message]
2006-05-11 2:31 ` Dave Jones
2006-05-11 4:01 ` Carl-Daniel Hailfinger
2006-05-11 15:17 ` Carl-Daniel Hailfinger
2006-05-11 15:28 ` Matthew Garrett
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=44625CE9.2060204@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=thoenig@suse.de \
--cc=trenn@suse.de \
/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