Reviewed-By: Joe Konno
On 09/29/2014 03:49 PM, U. Artie Eoff wrote:
> 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.
>
September 30, 2014 9:32 AM
> > > To: Eoff, Ullysses A
> > > Cc: dan...@ffwll.ch; intel-gfx@lists.freedesktop.org
> > > Subject: Re: [Intel-gfx] [PATCH 1/2 v3] drm/i915: intel_backlight scale()
> > > math WA
> > >
> > > On Tue, Sep 30, 2014 at 0
> Cc: dan...@ffwll.ch; intel-gfx@lists.freedesktop.org
> > Subject: Re: [Intel-gfx] [PATCH 1/2 v3] drm/i915: intel_backlight scale()
> > math WA
> >
> > On Tue, Sep 30, 2014 at 02:58:54PM +, Eoff, Ullysses A wrote:
> > > On Tue, 2014-09-30 at 10:04 +0200, Dan
> -Original Message-
> From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
> Sent: Tuesday, September 30, 2014 9:32 AM
> To: Eoff, Ullysses A
> Cc: dan...@ffwll.ch; intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] [PATC
On Tue, Sep 30, 2014 at 02:58:54PM +, Eoff, Ullysses A wrote:
> On Tue, 2014-09-30 at 10:04 +0200, Daniel Vetter wrote:
> > On Mon, Sep 29, 2014 at 03:49:32PM -0700, U. Artie Eoff wrote:
> > > Improper truncated integer division in the scale() function causes
> > > actual_brightness != brightne
On Tue, 2014-09-30 at 10:04 +0200, Daniel Vetter wrote:
> On Mon, Sep 29, 2014 at 03:49:32PM -0700, U. Artie Eoff wrote:
> > Improper truncated integer division in the scale() function causes
> > actual_brightness != brightness. This (partial) work-around should be
> > sufficient for a majority of
On Mon, Sep 29, 2014 at 03:49:32PM -0700, U. Artie Eoff wrote:
> 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.
>
> TOD
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
