intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: intel-gfx@lists.freedesktop.org, drm-intel-fixes@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Ignore panel type from OpRegion on SKL
Date: Wed, 13 Jul 2016 16:36:16 +0300	[thread overview]
Message-ID: <20160713133616.GZ4329@intel.com> (raw)
In-Reply-To: <1468416780.2265.5.camel@HansenPartnership.com>

On Wed, Jul 13, 2016 at 10:33:00PM +0900, James Bottomley wrote:
> On Tue, 2016-07-12 at 15:00 +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > Dell XPS 13 9350 apparently doesn't like it when we use the panel
> > type
> > from OpRegion. The OpRegion panel type (0) tells us to use use low
> > vswing for eDP, whereas the VBT panel type (2) tells us to use normal
> > vswing. The problem is that low vswing results in some display
> > flickers.
> > Since no one seems to know how this stuff is supposed to be handled,
> > let's just ignore the OpRegion panel type on SKL for now.
> > 
> > Reported-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> > Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
> > Cc: drm-intel-fixes@lists.freedesktop.org
> > References: https://lists.freedesktop.org/archives/intel-gfx/2016-Jun
> > e/098826.html
> > Fixes: a05628195a0d ("drm/i915: Get panel_type from OpRegion panel
> > details")
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> This one doesn't actually compile on git head:
> 
> 
> drivers/gpu/drm/i915/intel_opregion.c: In function
> ‘intel_opregion_get_panel_type’:
> drivers/gpu/drm/i915/intel_opregion.c:1047:17: error: ‘dev_priv’
> undeclared (first use in this function)
>   if (IS_SKYLAKE(dev_priv))
> 
> So it's going to be hard to backport to stable.

s/dev_priv/dev/ is probably all that's needed.

> 
> However, I've applied it on top of the drm branch and there have been
> no flicker problems after 12h of use, so you can add a tested by from
> me if you want.

Thanks.

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-07-13 13:36 UTC|newest]

Thread overview: 44+ 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-07-12 12:00                                         ` [PATCH] drm/i915: Ignore panel type from OpRegion on SKL ville.syrjala
2016-07-13 12:04                                           ` Daniel Vetter
2016-07-13 13:09                                             ` Ville Syrjälä
2016-07-13 13:33                                           ` James Bottomley
2016-07-13 13:36                                             ` Ville Syrjälä [this message]
2016-07-14 13:12                                           ` Ville Syrjälä
2016-07-12 13:12                                         ` ✗ Ro.CI.BAT: warning for " Patchwork
2016-07-14 13:02                                           ` Ville Syrjälä
2016-09-11 14:10                                   ` [Intel-gfx] Bad flicker on skylake HQD due to code in the 4.7 merge window James Hogan
2016-09-13 13:59                                     ` Jani Nikula
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=20160713133616.GZ4329@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=drm-intel-fixes@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).