diff options
author | U. Artie Eoff <ullysses.a.eoff@intel.com> | 2014-09-29 15:49:32 -0700 |
---|---|---|
committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2014-10-06 16:47:24 +0200 |
commit | 673e7bbdb3920b62cfc6c710bea626b0a9b0f43a (patch) | |
tree | 374688115b4c6f01df23a1a8c08841b0e8cdd3e9 /drivers/gpu/Makefile | |
parent | ebb69c95175609990af708ec90c46530f5a2c819 (diff) | |
download | linux-673e7bbdb3920b62cfc6c710bea626b0a9b0f43a.tar.gz linux-673e7bbdb3920b62cfc6c710bea626b0a9b0f43a.tar.bz2 linux-673e7bbdb3920b62cfc6c710bea626b0a9b0f43a.zip |
drm/i915: intel_backlight scale() math WA
Improper truncated integer division in the scale() function causes
actual_brightness != brightness. This (partial) work-around should be
sufficient for a majority of use-cases, but it is by no means a complete
solution.
TODO: Determine how best to scale "user" values to "hw" values, and
vice-versa, when the ranges are of different sizes. That would be a
buggy scenario even with this work-around.
The issue was introduced in the following (v3.17-rc1) commit:
6dda730 drm/i915: respect the VBT minimum backlight brightness
Note that for easier backporting this commit adds a duplicated macro.
A follow-up cleanup patch rectifies this for 3.18+
v2: (thanks to Chris Wilson) clarify commit message, use rounded division
macro
v3: -DIV_ROUND_CLOSEST() fails to build with CONFIG_X86_32=y. (Jani)
-Use DIV_ROUND_CLOSEST_ULL() instead. (Damien)
-v1 and v2 originally authored by Joe Konno.
Signed-off-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
Cc: stable@vger.kernel.org
Reviewed-By: Joe Konno <joe.konno@intel.com>
[danvet: Add backporting note.]
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/Makefile')
0 files changed, 0 insertions, 0 deletions