From: Jani Nikula <jani.nikula@linux.intel.com>
To: James Hogan <james@albanarts.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
"Syrjala, Ville" <ville.syrjala@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window
Date: Tue, 13 Sep 2016 16:59:58 +0300 [thread overview]
Message-ID: <87bmzr2941.fsf@intel.com> (raw)
In-Reply-To: <CAAG0J98krLsGoG=Hp7LMz84+Tz5MSVNJgCYGO7i6n4nda+Q0Jg@mail.gmail.com>
On Sun, 11 Sep 2016, James Hogan <james@albanarts.com> wrote:
> I've just bisected a similar (same?) problem (slow increase and
> decrease of screen brightness with a period of a few seconds) to the
> same commit (this is on a Dell XPS 13 laptop)
>
> commit a05628195a0d9f3173dd9aa76f482aef692e46ee
> Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Date: Mon Apr 11 10:23:51 2016 +0300
>
> drm/i915: Get panel_type from OpRegion panel details
>
> the difference for me is that good commits used the acpi backlight,
> and bad ones used the intel backlight (/sys/class/backlight/). Its
> like intel_backlight is fighting with the firmware to control the
> backlight or something. Reverting the commit on v4.7.3 switches it
> back to the acpi backlight and all works nicely again.
>
> let me know if I can provide anything else to help debug.
Please try [1].
BR,
Jani.
[1] http://patchwork.freedesktop.org/patch/msgid/1473758539-21565-1-git-send-email-ville.syrjala@linux.intel.com
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-13 13:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 19:59 Bad flicker on skylake HQD due to code in the 4.7 merge window James Bottomley
2016-05-31 7:51 ` Jani Nikula
2016-05-31 13:33 ` James Bottomley
2016-06-13 10:14 ` Jani Nikula
2016-06-16 21:15 ` James Bottomley
2016-06-16 21:24 ` Daniel Vetter
2016-06-16 21:29 ` [Intel-gfx] " James Bottomley
2016-06-16 22:42 ` James Bottomley
2016-06-17 7:28 ` Daniel Vetter
2016-06-17 13:34 ` Jani Nikula
2016-06-17 16:08 ` [Intel-gfx] " James Bottomley
2016-06-17 23:06 ` James Bottomley
2016-06-19 21:53 ` James Bottomley
2016-06-20 8:03 ` [Intel-gfx] " Jani Nikula
2016-06-21 13:53 ` James Bottomley
2016-06-21 15:44 ` Ville Syrjälä
2016-06-21 21:00 ` James Bottomley
2016-06-23 11:25 ` [Intel-gfx] " James Bottomley
2016-07-02 6:24 ` Thorsten Leemhuis
2016-07-07 16:14 ` [Intel-gfx] " Ville Syrjälä
2016-07-07 16:55 ` James Bottomley
2016-07-07 19:19 ` James Bottomley
2016-07-08 10:19 ` Ville Syrjälä
2016-07-08 14:48 ` James Bottomley
2016-07-08 16:56 ` Ville Syrjälä
2016-09-11 14:10 ` [Intel-gfx] " James Hogan
2016-09-13 13:59 ` Jani Nikula [this message]
2016-06-23 12:52 ` Steven Newbury
2016-06-23 12:59 ` Jani Nikula
2016-06-23 13:14 ` Steven Newbury
2016-06-24 10:59 ` Chris Wilson
2016-06-24 11:48 ` [Intel-gfx] " Steven Newbury
2016-06-24 12:42 ` Chris Wilson
2016-07-12 10:08 ` Daniel Vetter
2016-09-14 9:43 ` Jani Nikula
2016-06-17 8:12 ` Chris Wilson
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=87bmzr2941.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=james@albanarts.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=ville.syrjala@intel.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