From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: garland.owen@gmail.com, stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: Dell Chromebook 11 has PWM backlight
Date: Thu, 19 Feb 2015 11:00:54 +0200 [thread overview]
Message-ID: <87sie2qnqx.fsf@intel.com> (raw)
In-Reply-To: <1424336019-8725-1-git-send-email-jani.nikula@intel.com>
On Thu, 19 Feb 2015, Jani Nikula <jani.nikula@intel.com> wrote:
> Add quirk for Dell Chromebook 11 backlight.
Also
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=93451
> Tested-by: Owen Garland <garland.owen@gmail.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 3b0fe9f1f3c9..d630ce46298a 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -13100,6 +13100,9 @@ static struct intel_quirk intel_quirks[] = {
>
> /* HP Chromebook 14 (Celeron 2955U) */
> { 0x0a06, 0x103c, 0x21ed, quirk_backlight_present },
> +
> + /* Dell Chromebook 11 */
> + { 0x0a06, 0x1028, 0x0a35, quirk_backlight_present },
> };
>
> static void intel_init_quirks(struct drm_device *dev)
> --
> 2.1.4
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-02-19 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 8:53 [PATCH] drm/i915: Dell Chromebook 11 has PWM backlight Jani Nikula
2015-02-19 9:00 ` Jani Nikula [this message]
2015-02-23 13:15 ` [Intel-gfx] " Jani Nikula
2015-02-19 13:16 ` shuang.he
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=87sie2qnqx.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=garland.owen@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=stable@vger.kernel.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