From: Aaron Lu <aaron.lu@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
Nico Schottelius <nico-bugzilla.kernel.org@schottelius.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v2] drm/i915: restore backlight precision when converting from opregion
Date: Sun, 04 May 2014 15:31:01 +0800 [thread overview]
Message-ID: <5365ECB5.5070003@intel.com> (raw)
In-Reply-To: <20140504072232.GA22557@nuc-i3427.alporthouse.com>
On 05/04/2014 03:22 PM, Chris Wilson wrote:
> On Sun, May 04, 2014 at 03:16:05PM +0800, Aaron Lu wrote:
>> On 04/28/2014 09:41 PM, Daniel Vetter wrote:
>>> 64bit divisions won't compile on 32bit. You need one of the DO_DIV macros,
>>> or whatever they're called again. I pain, I know ;-)
>>
>> Thanks for the correction, here is an updated patch :-)
>>
>> From: Aaron Lu <aaron.lu@intel.com>
>> Date: Mon, 28 Apr 2014 11:02:52 +0800
>> Subject: [PATCH v2] drm/i915: restore backlight precision when converting from
>> ACPI
>>
>> When we set backlight on behalf of ACPI opregion, we will convert the
>> backlight value in the 0-255 range defined in opregion to the actual
>> hardware level. Commit 22505b82a2 (drm/i915: avoid brightness overflow
>> when doing scale) is meant to fix the overflow problem when doing the
>> conversion, but it also caused a problem that the converted hardware
>> level doesn't quite represent the intended value: say user wants maximum
>> backlight level(255 in opregion's range), then we will calculate the
>> actual hardware level to be: level = freq / max * level, where freq is
>> the hardware's max backlight level(937 on an user's box), and max and
>> level are all 255. The converted value should be 937 but the above
>> calculation will yield 765.
>>
>> To fix this issue, just use 64 bits to do the calculation to keep the
>> precision and avoid overflow at the same time.
>>
>> Buglink: https://bugzilla.kernel.org/show_bug.cgi?id=72491
>> Reported-by: Nico Schottelius <nico-bugzilla.kernel.org@schottelius.org>
>> Signed-off-by: Aaron Lu <aaron.lu@intel.com>
>> ---
>> v2: use do_div as reminded by Daniel.
>>
>> drivers/gpu/drm/i915/intel_panel.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
>> index a953b081ee38..8725917a3d0d 100644
>> --- a/drivers/gpu/drm/i915/intel_panel.c
>> +++ b/drivers/gpu/drm/i915/intel_panel.c
>> @@ -492,6 +492,7 @@ void intel_panel_set_backlight(struct intel_connector *connector, u32 level,
>> enum pipe pipe = intel_get_pipe_from_connector(connector);
>> u32 freq;
>> unsigned long flags;
>> + u64 n;
>>
>> if (!panel->backlight.present || pipe == INVALID_PIPE)
>> return;
>> @@ -502,10 +503,9 @@ void intel_panel_set_backlight(struct intel_connector *connector, u32 level,
>>
>> /* scale to hardware max, but be careful to not overflow */
>> freq = panel->backlight.max;
>> - if (freq < max)
>> - level = level * freq / max;
>> - else
>> - level = freq / max * level;
>> + n = level * freq;
>
> 32b * 32b = 32b
>
> n = (u64)level * freq; to avoid overflow as you claim.
Ah...yes, my fault, thanks.
>
> Also this still has the same rounding error as before.
I didn't get this, care to explain?
next prev parent reply other threads:[~2014-05-04 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 3:19 [PATCH] drm/i915: restore backlight precision when converting from opregion Aaron Lu
2014-04-28 13:41 ` Daniel Vetter
2014-05-04 7:16 ` [PATCH v2] " Aaron Lu
2014-05-04 7:22 ` Chris Wilson
2014-05-04 7:31 ` Aaron Lu [this message]
2014-05-04 10:41 ` Chris Wilson
2014-05-05 1:40 ` [Intel-gfx] " Aaron Lu
2014-05-12 8:55 ` [PATCH v3] " Aaron Lu
2014-05-15 8:59 ` Jani Nikula
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=5365ECB5.5070003@intel.com \
--to=aaron.lu@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=nico-bugzilla.kernel.org@schottelius.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.