Bug 24548 - S3 suspending supports for Ironlake graphics
Summary: S3 suspending supports for Ironlake graphics
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Wang Zhenyu
QA Contact:
URL:
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2009-10-15 02:33 UTC by minskey
Modified: 2017-07-24 23:09 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Fix LVDS black screen issue after resuming from S3 (11.75 KB, patch)
2009-10-15 02:33 UTC, minskey
no flags Details | Splinter Review

Description minskey 2009-10-15 02:33:47 UTC
Created attachment 30445 [details] [review]
Fix  LVDS black screen issue after resuming from S3

I get a system based Arrandale. With the following Zhenyu's 4 patches,  it can work but after resuming from S3,  LVDS has no outputs.

[PATCH 1/2] drm/i915: Fix FDI M/N setting according with correct color depth
[PATCH 2/2] drm/i915: disable powersave feature for Ironlake currently
[PATCH 3/3] drm/i915: fix to setup display reference clock control on Ironlake
[PATCH] drm/i915: Fix LVDS for Ironlake when assigned to pipe A,


I try to cook out a patch,  it works. See the attachment.
Comment 1 Wang Zhenyu 2009-11-05 22:14:21 UTC
Patch is already in upstream linus kernel. Close.

commit 4204878179c99d419d392d78d817729992b4c442
Author: Zhenyu Wang <zhenyuw@linux.intel.com>
Date:   Wed Oct 21 15:27:01 2009 +0800

    drm/i915: Ironlake suspend/resume support
    
    This adds registers save/restore for Ironlake to make suspend work.
    
    Signed-off-by: Guo, Chaohong <chaohong.guo@intel.com>
    [zhenyuw: some code re-orgnization, and add more save/restore for
    FDI link and transcoder registers, also fix palette register for Ironlake]
    Signed-off-by: Zhenyu Wang <zhenyuw@linux.intel.com>
    Signed-off-by: Eric Anholt <eric@anholt.net>


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.