From: Bernhard Froemel <froemel@vmars.tuwien.ac.at>
To: Matthew Garrett <mjg@redhat.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH V2 2/2] apple_gmux: Add support for newer hardware
Date: Tue, 14 Aug 2012 19:11:19 +0200 [thread overview]
Message-ID: <502A86B7.8010402@vmars.tuwien.ac.at> (raw)
In-Reply-To: <20120814151543.GD18992@thinkpad-t410>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/14/2012 05:15 PM, Seth Forshee wrote:
> On Tue, Aug 14, 2012 at 04:53:47PM +0200, Bernhard Froemel wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> Only in relation to Seth's future apple-gmux patch series about
>> vgaswitcheroo and restoring the gmux device configuration across
>> suspend/resume [1]: On resume the gmux registers 0x28 (DDC) and
>> 0x10 (SWITCH_DISPLAY) (i.e., the first two writes) are not
>> restored (result: the screen remains black after
>> suspend/resume).
>>
>> Of course, this does not happen with my patch proposal ;)
>> Unfortunately, I have not the time to sort this out in the next
>> couple of days -- on the other hand this is probably not a
>> problem w.r.t. this patch, but needs to be taken care of in
>> Seth's patch series.
>
> The patch adding support for switcheroo *does* restore those
> registers on resume. Are you saying that isn't happening when you
> use it?
Yes, the 8bit writes don't seem to get all through with Matthew's
patch, but they do with mine.
Just tested manual switching (/sys/kernel/debug/vgaswitcheroo/switch,
from IGD to DIS) -> doesn't work either; even locks up my system:
> [ 123.680062] hda-intel: spurious response 0x407381:0x0, last
> cmd=0x770883 [ 123.680070] hda-intel: spurious response
> 0x9000094:0x0, last cmd=0x770883 [ 123.680073] hda-intel: spurious
> response 0x185600f0:0x0, last cmd=0x770883 [ 123.680076]
> hda-intel: spurious response 0x4:0x0, last cmd=0x770883 [
> 123.680079] hda-intel: spurious response 0xb0a0908:0x0, last
> cmd=0x770883 [ 123.680082] hda-intel: spurious response
> 0x407381:0x0, last cmd=0x770883 [ 123.680084] hda-intel: spurious
> response 0x9000094:0x0, last cmd=0x770883 [ 123.680087] hda-intel:
> spurious response 0x185600f0:0x0, last cmd=0x770883
While comparing our patches, I discovered that mine isnt' a good
reference here, because in my ready and complete function variants I
didn't write/read the correct ioports (forgot about the offset; so
they were only slightly delaying execution). After I fixed that (and a
status-bit semantic mixup), the results appear similar :/
Need to play around further..
Bernhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAqhrcACgkQ6iVUjPs37JnhtwCePUp7sLQW+GhBFOkFbkjr6Yrh
VAsAoJ3TjtJu2gQpayFc6iP5nBQfdAPG
=ziXd
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-08-14 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 22:52 [PATCH V2 1/2] gmux: Add generic write32 function Matthew Garrett
2012-08-13 22:52 ` [PATCH V2 2/2] apple_gmux: Add support for newer hardware Matthew Garrett
2012-08-14 0:46 ` Seth Forshee
2012-08-14 14:05 ` Bernhard Froemel
2012-08-14 14:53 ` Bernhard Froemel
2012-08-14 15:15 ` Seth Forshee
2012-08-14 17:11 ` Bernhard Froemel [this message]
2012-08-15 7:46 ` Bernhard Froemel
2012-08-14 0:44 ` [PATCH V2 1/2] gmux: Add generic write32 function Seth Forshee
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=502A86B7.8010402@vmars.tuwien.ac.at \
--to=froemel@vmars.tuwien.ac.at \
--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
all inboxes | Powered by JetHome®