From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Len Brown <lenb@kernel.org>,
Gabriel C <nix.or.die@googlemail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pm@lists.linux-foundation.org, pavel@suse.cz
Subject: Re: Some sort corruption of my Thermal Subsystem after suspend to ram
Date: Thu, 1 May 2008 14:57:49 +0200 [thread overview]
Message-ID: <200805011457.51238.rjw@sisk.pl> (raw)
In-Reply-To: <20080501125348.GA19922@srcf.ucam.org>
On Thursday, 1 of May 2008, Matthew Garrett wrote:
> On Thu, May 01, 2008 at 01:57:58AM -0400, Len Brown wrote:
>
> > I'm not aware of a native Linux device driver that talks to this device
> > (nor can I think of a useful purpose for such a driver)
> > So it seems what is in play here is any BIOS code that talks to this device,
> > and Linux's standard PCI config space restore.
>
> Perhaps we should be more aggressive about restoring PCI config space if
> there's no driver bound to a device. The alternative in this case would
> seem to be to write a driver for this device that does nothing other
> than handle suspend/resume.
Well, we have default suspend/resume for PCI devices. They are called for
devices that have no drivers bound to them and execute
pci_restore_state()/pci_restore_state(), among other things. Isn't that
sufficient?
Rafael
next prev parent reply other threads:[~2008-05-01 12:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 20:42 Gabriel C
2008-04-30 20:46 ` Jay Cliburn
2008-04-30 20:59 ` Gabriel C
2008-04-30 21:02 ` Jay Cliburn
2008-05-01 5:57 ` Len Brown
2008-05-01 12:53 ` Matthew Garrett
2008-05-01 12:57 ` Rafael J. Wysocki [this message]
2008-05-01 13:06 ` Matthew Garrett
2008-05-01 17:14 ` Rafael J. Wysocki
2008-05-01 13:19 ` Gabriel C
2008-05-01 16:09 ` Pavel Machek
2008-05-01 16:30 ` Alan
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=200805011457.51238.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mjg59@srcf.ucam.org \
--cc=nix.or.die@googlemail.com \
--cc=pavel@suse.cz \
/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
all inboxes | Powered by JetHome®