From: Stefan Seyfried <seife@suse.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Miroslav Ruda <ruda@ics.muni.cz>,
linux-acpi@vger.kernel.org,
suspend-devel List <suspend-devel@lists.sourceforge.net>
Subject: Re: suspend to RAM on lifebook 7110
Date: Mon, 18 Dec 2006 12:29:16 +0100 [thread overview]
Message-ID: <20061218112916.GB6636@suse.de> (raw)
In-Reply-To: <20061218111142.GA27070@srcf.ucam.org>
Hi Matthew,
thanks for explaining this, i am obviously not too deep into that
PCI bus stuff :-)
On Mon, Dec 18, 2006 at 11:11:42AM +0000, Matthew Garrett wrote:
> On Mon, Dec 18, 2006 at 07:51:36AM +0100, Stefan Seyfried wrote:
>
> > I thought that this should somehow go away by the PCI bus suspend/resume
> > methods that somewhen back got merged by Greg K-H.
>
> The kernel will only save and restore the standardised PCI configuration
> registers - anything else needs to be handled by the specific device
> driver. Unfortunately, in the graphics hardware case, the closest thing
> to that is the framebuffer driver. Which we don't tend to use.
So the question is: should we either
- implement a minimal "graphics card PCI suspend resume" "driver" in the
kernel that will do this even if no framebuffer is used, or
- implement this as a workaround in userspace?
I mean - it is not rocket science to do it in s2ram, but it just seems
more correct (to me) to do it in the kernel, where the correct locking
and ordering is more or less guaranteed.
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-12-18 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 12:33 suspend to RAM on lifebook 7110 Frank Ursel
2006-12-08 21:13 ` Miroslav Ruda
2006-12-18 6:51 ` Stefan Seyfried
2006-12-18 11:11 ` Matthew Garrett
2006-12-18 11:29 ` Stefan Seyfried [this message]
2006-12-18 12:05 ` Matthew Garrett
2006-12-18 17:48 ` Stefan Seyfried
2006-12-18 20:00 ` Rafael J. Wysocki
2006-12-18 12:16 ` Pavel Machek
2006-12-18 15:55 ` Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2006-12-07 22:18 Miroslav Ruda
2006-12-18 6:38 ` Stefan Seyfried
2006-12-18 9:30 ` Frank Ursel
2006-12-18 16:53 ` Miroslav Ruda
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=20061218112916.GB6636@suse.de \
--to=seife@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=ruda@ics.muni.cz \
--cc=suspend-devel@lists.sourceforge.net \
/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