From: Daniel Vetter <daniel@ffwll.ch>
To: Aaron Plattner <aplattner@nvidia.com>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [i915] Backlight brighter since 3.9.0
Date: Mon, 3 Jun 2013 21:36:20 +0200 [thread overview]
Message-ID: <20130603193619.GU15743@phenom.ffwll.local> (raw)
In-Reply-To: <51ACC09E.9070404@nvidia.com>
On Mon, Jun 03, 2013 at 09:13:18AM -0700, Aaron Plattner wrote:
> On 05/20/2013 02:55 PM, Daniel Vetter wrote:
> >On Sat, May 18, 2013 at 12:39:14AM +0200, Jan Hinnerk Stosch wrote:
> >>Hallo,
> >>
> >>I hope this is the right place to ask, because I actually don't know
> >>whether it is a bug or a feature that I'm experiencing since linux 3.9:
> >>When I boot my system the backlight gets extremely bright compared to older
> >>kernel versions. It is most obvious when I leave X (more a yellow than a
> >>black background), but I have the impression, that the colors in X are
> >>brighter than usual, too.
> >>I used my spare time this afternoon to do a kernel bisect and learned that
> >>the first "bad" commit is 55bc60db5988c8366751d3d04dd690698a53412c. As I
> >>don't have insight or understanding of the code: Is this behaviour intended
> >>and how could I change it to the old state or is it a bug and should I
> >>report it somewhere?
> >>My system is as follows:
> >>Intel i5-3570k with Intel HD 4000
> >>my monitor is connected via HDMI.
> >>If you need any more information just tell me.
> >
> >Yeah, this is a feature. HDMI has (for oddball backwards compat with
> >analog TV signals) a special mode which reduces the useable RGB value
> >range by chopping off about 10% at the bottom and top end. This results in
> >light colors getting brighter and dark colors getting darker.
> >
> >The above mentioned commit tries (to the best of our knowledge) to
> >auto-set the option which most likely fits what the hdmi sink will do with
> >the color data. You can either fix this up in the hdmi sink with the
> >on-screen menu or by manually setting the "RBG Broadcast" property for the
> >relevant hdmi connector to the setting you want.
>
> This property seems like it's generally useful for all GPUs that
> support range compression. Has anyone started the process of adding
> it to randrproto.txt as an official property?
>
> http://cgit.freedesktop.org/xorg/proto/randrproto/tree/randrproto.txt#n1723
Oops, I didn't know that we have some properties standardized there,
especially since the existing pile of drm/kms drivers seem to only lously
follow them. Should we move this into the kernel since that's essentially
the place that defines them?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-06-03 19:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 22:39 [i915] Backlight brighter since 3.9.0 Jan Hinnerk Stosch
2013-05-20 21:55 ` Daniel Vetter
2013-05-21 6:29 ` Jan Hinnerk Stosch
2013-05-22 16:08 ` Joakim Plate
2013-05-22 16:56 ` Daniel Vetter
2013-06-03 16:13 ` Aaron Plattner
2013-06-03 19:36 ` Daniel Vetter [this message]
2013-06-03 19:42 ` Aaron Plattner
2013-06-03 20:03 ` Daniel Vetter
2013-06-03 21:10 ` Alex Deucher
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=20130603193619.GU15743@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=aplattner@nvidia.com \
--cc=dri-devel@lists.freedesktop.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