linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Deucher <alexdeucher@gmail.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	David John <davidjon@xenontk.org>,
	Johan Hovold <jhovold@gmail.com>,
	linux-kernel@vger.kernel.org, Dave Airlie <airlied@redhat.com>,
	dri-devel@lists.sourceforge.net
Subject: Re: [PATCH] drm/kms: fix fbdev blanking regression
Date: Wed, 13 Jan 2010 15:01:00 -0500	[thread overview]
Message-ID: <a728f9f91001131201k6ba53710jdf85c1e38a937901@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1001131947340.17662@casper.infradead.org>

On Wed, Jan 13, 2010 at 2:48 PM, James Simmons <jsimmons@infradead.org> wrote:
>
>> > > On 01/07/2010 12:42 AM, Johan Hovold wrote:
>> > > >> Yeap. The fix uncovered a bug in your driver. I haven't heard of
>> > > >> problems with the other drm drivers.
>> > > >>
>> > > >>> The backlight is handled via the DRI driver I assume. At least
>> > > >>> i9xx_crtc_dpms is called on powerdown.
>> > > >>
>> > > >> Can you post your dmesg and kernel config.
>> > >
>> > > [snip]
>> > >
>> > > Adding the Intel DRM people in CC as well. I have the same issue
>> > > with my GM45.
>> >
>> > Okay I looked at the code to figure out what is happening and why
>> > only this driver has problems. The problem is that the framebuffer
>> > layer expects the backlight to be a seperate device. The reason being
>> > is that some embedded systems will use a gpio backlight. That way
>> > power management for a graphics card/backlight has 3 seperate states.
>> > Currently the intel DRM driver treats the backlight as being apart of
>> > the encoder. Jesse do you have objections to having the intel driver
>> > expose a backlight device. The bonus of that is the user can also set
>> > the backlight levels.
>>
>> On Intel we usually expect the backlight to be exposed by ACPI or a
>> platform driver.  On recent platforms, the ACPI driver will actually
>> send requests to the gfx driver to do the actual register writes to
>> adjust the backlight, but it's still ACPI driven.
>>
>> Maybe we just need to wire up the fb backlight hooks appropriately?
>
> Yeap. I can have patch ready for you this weekend. I lack the hardware to
> test it tho. Never been able to find a intel pci card that is not built
> into the motherboard.

They don't exist, other than the old i740s.

Alex

  reply	other threads:[~2010-01-13 20:01 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
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 [this message]
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=a728f9f91001131201k6ba53710jdf85c1e38a937901@mail.gmail.com \
    --to=alexdeucher@gmail.com \
    --cc=airlied@redhat.com \
    --cc=davidjon@xenontk.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jhovold@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).