From: Thomas Richter <richter@tik.uni-stuttgart.de>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Thomas Richter <richter@rus.uni-stuttgart.de>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: R31 dithering
Date: Mon, 30 Mar 2015 16:06:33 +0200 [thread overview]
Message-ID: <55195869.40805@tik.uni-stuttgart.de> (raw)
In-Reply-To: <20150330135922.GM17410@intel.com>
Am 30.03.2015 um 15:59 schrieb Ville Syrjälä:
> On Mon, Mar 30, 2015 at 03:54:29PM +0200, Thomas Richter wrote:
>> Am 30.03.2015 um 13:55 schrieb Ville Syrjälä:
>>> On Fri, Mar 27, 2015 at 07:57:52PM +0100, Thomas Richter wrote:
>>
>>>> Thanks and have a nice weekend,
>>>
>>> BTW I think this bug is about failure to restore the ivch to proper
>>> state after suspend (on X30): https://bugs.freedesktop.org/show_bug.cgi?id=49838
>>> Just in case you're looking for more stuff to do around the ivch ;)
>>
>> Well, no x30 around here unfortunately, though I can possibly check for
>> helpers in a German Thinkpad forum. Maybe somebody with enough
>> Linux-awareness can remote-debug and provide a couple of register
>> listings to re-enable the DVO as required during wake-up. Or provides an
>> x30. (-:
>>
>> I'll check and let you know.
>
> I was assuming your R31 or whatever would have the same problems.
No, astonishingly, not. Suspend/resume and hibernate work fine. Well,
somewhat... Actually, the R31 only supports S1 (standby) correctly and
not S3 (suspend to RAM), even though ACPI (the DSDT) makes you believe
that S3 would work.
Problem is that the bios does not even enter the kernel anymore once you
wake it up from S3 - it's completely dead then and the user mode entry
point of the kernel is never reached. So the kernel can hardly do
anything about this in first place.... I personally "solved" the problem
by providing a custom DSDT which just disables S3, and it worked happily
ever after...
Greetings,
Thomas
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2015-03-30 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 8:03 Addressing the intel VCH on the i2c bus / R31 dithering Thomas Richter
2015-03-27 8:40 ` Daniel Vetter
2015-03-27 9:33 ` Ville Syrjälä
2015-03-27 18:57 ` Thomas Richter
2015-03-30 11:55 ` Ville Syrjälä
2015-03-30 13:54 ` Thomas Richter
2015-03-30 13:59 ` Ville Syrjälä
2015-03-30 14:06 ` Thomas Richter [this message]
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=55195869.40805@tik.uni-stuttgart.de \
--to=richter@tik.uni-stuttgart.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=richter@rus.uni-stuttgart.de \
--cc=ville.syrjala@linux.intel.com \
/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