public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Grant Likely <grant.likely@secretlab.ca>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: Grant Likely <grant.likely@secretlab.ca>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	David Airlie <airlied@linux.ie>, Matthew Garrett <mjg@redhat.com>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] i915: Quirk out disconnected backlight
Date: Fri, 14 Sep 2012 14:01:32 +0100	[thread overview]
Message-ID: <84c8a8$5o3dgr@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1347627426-3813-1-git-send-email-grant.likely@secretlab.ca>

On Fri, 14 Sep 2012 13:57:06 +0100, Grant Likely <grant.likely@secretlab.ca> wrote:
> Some platforms (for instance MacbookPros) have custom backlight drivers
> and don't use the integrated i915 backlight control. This patch adds a
> quirk to disable registering the intel backlight when unused on a
> platform.
> 
> Tested on MacbookPro8,3. Without this patch both the intel_backlight and
> gmux_backlight devices get registered and userspace doesn't know which
> it should use.

Userspace is informed throught the backlight/type property.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-09-14 13:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14 12:57 [PATCH] i915: Quirk out disconnected backlight Grant Likely
2012-09-14 13:01 ` Chris Wilson [this message]
2012-09-14 13:09   ` Grant Likely
2012-09-14 13:12     ` David Woodhouse
2012-09-14 13:24       ` Grant Likely
2012-09-17  8:03         ` Jani Nikula
2012-09-17 16:02           ` Grant Likely
2012-09-14 13:33       ` Chris Wilson
2012-09-14 13:48 ` Matthew Garrett
2012-09-14 14:29   ` David Woodhouse
2012-09-14 14:40     ` Matthew Garrett

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='84c8a8$5o3dgr@orsmga001.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=dwmw2@infradead.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    /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