From: Johan Hovold <jhovold@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Johan Hovold <jhovold@gmail.com>,
Dave Airlie <airlied@redhat.com>,
dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/kms: fix fbdev blanking regression
Date: Wed, 6 Jan 2010 19:09:50 +0100 [thread overview]
Message-ID: <20100106180950.GD10442@localhost> (raw)
In-Reply-To: <alpine.LFD.2.00.1001061710510.5372@casper.infradead.org>
> > Commit 731b5a15a3b1474a41c2ca29b4c32b0f21bc852e (drm/kms: properly
> > handle fbdev blanking) breaks console blanking on my laptop (GM45
> > chipset). Instead of blanking the screen, it is dimmed and then the
> > backlight starts "glowing" in the lower edges of the screen. The glowing
> > then slowly spreads upwards. Does not look healthy at all...
> >
> > This patch reverts to the old behaviour of going directly to
> > DPMS_STANDBY.
>
> The current fbdev blank is correct. Normal blanking doesn't power down
> the hsync or the vsync signals. If you look at fbdev drivers you will see
> this type of behavior. If you want a full power down then a FB_BLANK_POWERDOWN
> is needed. As for the blacklight that is a another problem not related to
> this issue. The fbdev layer sends a event to the backlight layer to tell
> it to power down. That powerdown happens for the backlight in all cases
> except FB_BLANK_UNBLANK. How is your backlight setup. Is the backlight
> handled via the DRI driver or acpi?
>
The change itself looks correct but it triggers something that seems to
hurt my screen bad. :)
The backlight is handled via the DRI driver I assume. At least
i9xx_crtc_dpms is called on powerdown.
next prev parent reply other threads:[~2010-01-06 18:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 17:00 [bisected] drm/ksm: fbdev blanking regression in 2.6.33 Johan Hovold
2010-01-06 17:00 ` [PATCH] drm/kms: fix fbdev blanking regression Johan Hovold
2010-01-06 17:33 ` James Simmons
2010-01-06 18:09 ` Johan Hovold [this message]
2010-01-06 18:18 ` James Simmons
2010-01-06 19:12 ` Johan Hovold
2010-01-07 6:41 ` David John
2010-01-12 17:28 ` James Simmons
2010-01-12 17:34 ` Jesse Barnes
2010-01-13 19:48 ` James Simmons
2010-01-13 20:01 ` Alex Deucher
2010-01-15 12:40 ` James Simmons
2010-01-15 13:10 ` Alan Cox
2010-01-16 16:02 ` James Simmons
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=20100106180950.GD10442@localhost \
--to=jhovold@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.