From: Seth Forshee <seth.forshee@canonical.com>
To: Arun Raghavan <arun.raghavan@collabora.co.uk>
Cc: Matthew Garrett <mjg@redhat.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] apple-gmux: Restore switch registers on suspend/resume
Date: Tue, 10 Jul 2012 08:35:37 -0500 [thread overview]
Message-ID: <20120710133537.GC10194@thinkpad-t410> (raw)
In-Reply-To: <1341891593-6485-1-git-send-email-arun.raghavan@collabora.co.uk>
On Tue, Jul 10, 2012 at 09:09:53AM +0530, Arun Raghavan wrote:
> After suspend and resume, the values of these registers seem to change
> from what they were at suspend time, potentially preventing the actual
> output lines from being enabled post-resume. This saves relevant state
> at suspend and restores it when resumed.
>
> This is at least required on the MacBook Pro 8.2 when the Intel GPU is
> manually selected in GRUB config before the kernel is loaded.
I've got a couple of problems with this. The first is that the backlight
update_status callback isn't an appropriate place to do this. Adding
suspend/resume ops for the pnp_driver would be better.
But the more serious concern is whether or not its safe to simply
restore the register values. I know that the reverse engineering work
done on the gmux has revealed a particular sequence for selecting the
active GPU. A brute force restoration of the registers disregards this
sequencing, which doesn't seem like a good idea.
Seth
next prev parent reply other threads:[~2012-07-10 13:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 3:39 [PATCH] apple-gmux: Restore switch registers on suspend/resume Arun Raghavan
2012-07-10 13:35 ` Seth Forshee [this message]
2012-07-10 16:05 ` Matthew Garrett
2012-07-10 16:35 ` Seth Forshee
2012-07-11 0:25 ` Andreas Heider
2012-07-29 0:42 ` David Woodhouse
2012-07-29 1:18 ` David Woodhouse
2012-07-29 7:46 ` Andreas Heider
2012-07-29 19:05 ` David Woodhouse
2012-07-29 19:34 ` Andreas Heider
2012-07-29 22:44 ` David Woodhouse
2012-07-30 14:05 ` Seth Forshee
2012-07-29 19:39 ` Matthew Garrett
2012-07-29 20:33 ` David Woodhouse
2012-07-29 20:52 ` David Woodhouse
2012-07-29 20:59 ` Matthew Garrett
2012-07-31 15:18 ` Seth Forshee
2012-07-31 17:07 ` Seth Forshee
2012-08-01 15:35 ` David Woodhouse
2012-08-01 15:59 ` Seth Forshee
2012-08-01 16:06 ` Andreas Heider
2012-08-01 19:41 ` David Woodhouse
2012-08-01 19:52 ` Seth Forshee
2012-08-01 19:43 ` David Woodhouse
2012-08-01 19:52 ` Matthew Garrett
2012-08-01 19:56 ` Seth Forshee
2012-08-01 19:56 ` Andreas Heider
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=20120710133537.GC10194@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=arun.raghavan@collabora.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
/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