All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Andrea Arcangeli" <aarcange@redhat.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Dave Airlie" <airlied@linux.ie>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge
Date: Mon, 29 Aug 2016 10:24:38 +0300	[thread overview]
Message-ID: <87h9a4rqa1.fsf@intel.com> (raw)
In-Reply-To: <1472398126-1095-2-git-send-email-aarcange@redhat.com>

On Sun, 28 Aug 2016, Andrea Arcangeli <aarcange@redhat.com> wrote:
> Skylake was already singled out, but it doesn't cover the XPS 13 L332X
> model which is based on IvyBridge.
>
> The commit that introduced the regression is
> 1d6da87a3241deb13d073c4125d19ed0e5a0c62c

That's a merge commit, the real one is

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 Skylake workaround for the regression was introduced in commit
> aeddda06c1a704bb97c8a7bfe7a472120193bd56
>
> Signed-off-by: Andrea Arcangeli <aarcange@redhat.com>
> ---
>  drivers/gpu/drm/i915/intel_opregion.c | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion.c
> index adca262..ca17ab6 100644
> --- a/drivers/gpu/drm/i915/intel_opregion.c
> +++ b/drivers/gpu/drm/i915/intel_opregion.c
> @@ -1073,12 +1073,14 @@ intel_opregion_get_panel_type(struct drm_i915_private *dev_priv)
>  	}
>  
>  	/*
> -	 * FIXME On Dell XPS 13 9350 the OpRegion panel type (0) gives us
> -	 * low vswing for eDP, whereas the VBT panel type (2) gives us normal
> -	 * vswing instead. Low vswing results in some display flickers, so
> -	 * let's simply ignore the OpRegion panel type on SKL for now.
> +	 * FIXME On Dell XPS 13 9350 and Dell XPS 13 L322X the
> +	 * OpRegion panel type (0) gives us low vswing for eDP,
> +	 * whereas the VBT panel type (2) gives us normal vswing
> +	 * instead. Low vswing results in some display flickers, so
> +	 * let's simply ignore the OpRegion panel type on SKL and
> +	 * IVYBRIDGE for now.
>  	 */

If it's an Iybridge, there's no low vswing, and that explanation is
false. You can verify by trying i915.edp_vswing=1 or i915.edp_vswing=2
on an unpatched kernel.

Doesn't mean there can't be something else wrong with the mode you get
using a different panel_type. And this makes me wonder what the point is
in trying to patch up the commit instead of reverting.


BR,
Jani.



> -	if (IS_SKYLAKE(dev_priv)) {
> +	if (IS_SKYLAKE(dev_priv) || IS_IVYBRIDGE(dev_priv)) {
>  		DRM_DEBUG_KMS("Ignoring OpRegion panel type (%d)\n", ret - 1);
>  		return -ENODEV;
>  	}
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-08-29  7:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 15:28 [PATCH 0/1] drm: i915: don't use OpRegion for XPS 13 IvyBridge Andrea Arcangeli
2016-08-28 15:28 ` [PATCH 1/1] " Andrea Arcangeli
2016-08-29  7:24   ` Jani Nikula [this message]
2016-08-29 13:32     ` Andrea Arcangeli
2016-08-29 15:08       ` Jani Nikula
2016-08-29 18:48     ` Andrea Arcangeli
2016-08-30  6:54       ` Martin van Es
2016-08-30  8:13         ` Jani Nikula
2016-08-30  9:13           ` Martin van Es
2016-08-30  7:25       ` Jani Nikula
2016-09-06  9:20   ` Ville Syrjälä
2016-09-06 10:56     ` Ville Syrjälä
2016-09-06 18:40       ` Ville Syrjälä
2016-09-08 10:04         ` Martin van Es
2016-09-08 10:18           ` Ville Syrjälä
2016-09-08 11:09             ` Martin van Es
2016-09-08 13:53               ` Andrea Arcangeli
2016-09-14  9:40 ` [PATCH 0/1] " 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=87h9a4rqa1.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=aarcange@redhat.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.