From: Jani Nikula <jani.nikula@linux.intel.com>
To: Grant Likely <grant.likely@secretlab.ca>,
David Woodhouse <dwmw2@infradead.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH] i915: Quirk out disconnected backlight
Date: Mon, 17 Sep 2012 11:03:30 +0300 [thread overview]
Message-ID: <87a9wp84a5.fsf@intel.com> (raw)
In-Reply-To: <CACxGe6szLVwsdNOvpB9v8pGDrygu+Go5Vf3bvpE19v3+Hkv4ww@mail.gmail.com>
On Fri, 14 Sep 2012, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Fri, Sep 14, 2012 at 2:12 PM, David Woodhouse <dwmw2@infradead.org> wrote:
>> See https://bugzilla.redhat.com/show_bug.cgi?id=752595
>
> In that bug you mention that the intel backlight sets a bogus max of
> '1' when a backlight isn't present. I saw that too here. Here's the
> offending code:
>
> u32 intel_panel_get_max_backlight(struct drm_device *dev)
> {
> struct drm_i915_private *dev_priv = dev->dev_private;
> u32 max;
>
> max = i915_read_blc_pwm_ctl(dev_priv);
> if (max == 0) {
> /* XXX add code here to query mode clock or hardware clock
> * and program max PWM appropriately.
> */
> pr_warn_once("fixme: max PWM is zero\n");
> return 1;
> }
>
> I used a quirk in my patch, but I could instead change the driver to
> bail here instead of trying to limp along.
Hi Grant, please try v3.6-rc6 that does exactly that with:
commit 28dcc2d60cb570d9f549c329b2f51400553412a1
Author: Jani Nikula <jani.nikula@intel.com>
Date: Mon Sep 3 16:25:12 2012 +0300
drm/i915: do not expose a dysfunctional backlight interface to userspace
Does that fix it for you?
BR,
Jani.
next prev parent reply other threads:[~2012-09-17 7:59 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
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 [this message]
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=87a9wp84a5.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--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