From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 16389] New PM-Code produces white screen on laptop display on startup on an radeon x700
Date: Tue, 20 Jul 2010 16:08:49 GMT [thread overview]
Message-ID: <201007201608.o6KG8njp025314@demeter.kernel.org> (raw)
In-Reply-To: <bug-16389-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16389
--- Comment #5 from Alex Deucher <alexdeucher@gmail.com> 2010-07-20 16:08:48 ---
(In reply to comment #4)
> Looking at fdo-bug 22755 i found another way to put the screen into an usable
> stae after resolution switch:
> xrandr -s 1024x768; xrandr --output LVDS --off; xrandr --output LVDS --auto
> works (i think it is the same call as vbetool dpms off / on).
> Without turning the output off and on i get the white screen. Whats the
> difference between boot-time initialization of the screen (which does not work)
> and the initialization with the xrandr off / on call (which works) ?
Nothing. Both use the same path in the driver. I suspect this is a timing
issue with the LVDS. Your system probably needs a longer/shorter delay
somewhere in the LVDS dpms code. Can you try adjusting the delays in
radeon_legacy_lvds_dpms() in radeon_legacy_encoders.c? Can you also try
something like this:
diff --git a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
index bad77f4..5688a0c 100644
--- a/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
+++ b/drivers/gpu/drm/radeon/radeon_legacy_encoders.c
@@ -108,6 +108,7 @@ static void radeon_legacy_lvds_dpms(struct drm_encoder
*encoder, int mode)
udelay(panel_pwr_delay * 1000);
WREG32(RADEON_LVDS_GEN_CNTL, lvds_gen_cntl);
WREG32_PLL(RADEON_PIXCLKS_CNTL, pixclks_cntl);
+ udelay(panel_pwr_delay * 1000);
break;
}
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
--
next prev parent reply other threads:[~2010-07-20 16:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 17:57 [Bug 16389] New: New PM-Code produces white screen on laptop display on startup on an radeon x700 bugzilla-daemon
2010-07-14 18:14 ` [Bug 16389] " bugzilla-daemon
2010-07-15 5:04 ` bugzilla-daemon
2010-07-15 5:05 ` bugzilla-daemon
2010-07-20 8:33 ` bugzilla-daemon
2010-07-20 16:08 ` bugzilla-daemon [this message]
2010-07-21 21:36 ` bugzilla-daemon
2010-07-21 22:22 ` bugzilla-daemon
2010-07-23 7:42 ` bugzilla-daemon
2010-07-23 11:28 ` bugzilla-daemon
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=201007201608.o6KG8njp025314@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-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