Re: [PATCH 3.8.y] drm/i915: add quirk to invert brightness on eMachines e725

[Jani Nikula]

On Tue, 09 Apr 2013, Josh Boyer <jwboyer@xxxxxxxxxx> wrote:
> Upstream commit 01e3a8feb40e54b962a20fa7eb595c5efef5e109

This patch seems to be the above commit and

commit 1ffff60320879830e469e26062c18f75236822ba
Author: Jani Nikula <jani.nikula@xxxxxxxxx>
Date:   Tue Jan 22 12:50:34 2013 +0200

    drm/i915: add quirk to invert brightness on eMachines G725

squashed together. There's a separate bug for that too:
https://bugs.freedesktop.org/show_bug.cgi?id=59628

I think both are okay for stable, but by the stable rules you should
probably split this up, with the appropriate upstream references in
both. Or do whatever the stable team tells you to do. ;)

BR,
Jani.

>
> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=31522#c35
> [Note: There are more than one broken setups in the bug. This fixes one.]
> Reported-by: Martins <andrissr@xxxxxxxx>
> Signed-off-by: Jani Nikula <jani.nikula@xxxxxxxxx>
> Signed-off-by: Daniel Vetter <daniel.vetter@xxxxxxxx>
> ---
>  drivers/gpu/drm/i915/intel_display.c | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index e6e4df7..6292677 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -8899,6 +8899,12 @@ static struct intel_quirk intel_quirks[] = {
>  	/* Acer Aspire 5734Z must invert backlight brightness */
>  	{ 0x2a42, 0x1025, 0x0459, quirk_invert_brightness },
>  
> +	/* Acer/eMachines G725 */
> +	{ 0x2a42, 0x1025, 0x0210, quirk_invert_brightness },
> +
> +	/* Acer/eMachines e725 */
> +	{ 0x2a42, 0x1025, 0x0212, quirk_invert_brightness },
> +
>  	/* Acer Aspire 4736Z */
>  	{ 0x2a42, 0x1025, 0x0260, quirk_invert_brightness },
>  };
> -- 
> 1.8.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/