From: James Hogan <james@albanarts.com>
To: Jani Nikula <jani.nikula@intel.com>,
Imre Deak <imre.deak@intel.com>,
Kamal Mostafa <kamal@canonical.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: drm/i915: XPS13 backlight regression in v3.14
Date: Thu, 03 Apr 2014 04:12:58 +0100 [thread overview]
Message-ID: <2613018.1cXJgVWlHm@radagast> (raw)
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Hi,
I've noticed that v3.14 breaks the backlight on Dell XPS13. Reverting the
following commit fixes the issue for me (i.e. the GUI brightness controls work
again):
bc0bb9fd1c78 drm/i915: remove QUIRK_NO_PCH_PWM_ENABLE
It appears that in v3.14 (with the above patch):
* intel_backlight/brightness=4882 (max & default) causes
acpi_video0/brightness to have no effect.
* intel_backlight/brightness=0 causes acpi_video0/brightness to behave
corrrectly (the firmware (I assume) fades the brightness gradually when
acpi_video0/brightness is set)
* intel_backlight/brightness=something else in between often causes
acpi_video0 and intel_backlight to apparently "fight" over the backlight,
resulting in brightness flickering up and down every second or so.
Reverting the above patch on v3.14:
* intel_backlight/brightness has no effect
* acpi_video0/brightness works normally
It doesn't seem quite as simple as them trying to use the same hardware since
when intel_backlight/brightness=4882, acpi_video0/brightness has no effect at
all, so I don't really get what's going on.
Can anybody shed some light or suggest a proper fix for this recurring issue?
Thanks
James
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-04-03 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 3:12 James Hogan [this message]
2014-04-03 7:02 ` Jani Nikula
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=2613018.1cXJgVWlHm@radagast \
--to=james@albanarts.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=kamal@canonical.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®