dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Mihai Donțu" <mihai.dontu@gmail.com>,
	"Rodrigo Vivi" <rodrigo.vivi@gmail.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	"Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: i915: screen flicker
Date: Thu, 28 Apr 2016 11:02:13 +0300	[thread overview]
Message-ID: <87mvoei2ka.fsf@intel.com> (raw)
In-Reply-To: <20160427204207.640e5410@mdontu-l.dsd.bitdefender.biz>

On Wed, 27 Apr 2016, Mihai Donțu <mihai.dontu@gmail.com> wrote:
> On Wed, 27 Apr 2016 20:36:13 +0300 Mihai Donțu wrote:
>> On Wed, 27 Apr 2016 08:28:20 -0700 Rodrigo Vivi wrote:
>> > Hi Mihai,
>> > 
>> > What platform do you have? HSW or BDW?  
>> 
>> I have an i7, Haswell CPU.
>> 
>> > If you don't know please provide lspci -nn  
>> 
>> I have attached the output of lspci, just in case. :-)
>> 
>> > What happens if you boot with i915.enable_psr=2?  
>> 
>> I'll try now.
>
> The behaviour is worse now. The screen flickers every couple of seconds.

Another report, please move the discussion there:

https://bugs.freedesktop.org/show_bug.cgi?id=95176

Thanks,
Jani.

>
>> > In case it helps, could you please boot with default
>> > i915.enable_psr=-1 appying this patch to your kernel to know what your
>> > VBT recommends:
>> > diff --git a/drivers/gpu/drm/i915/intel_psr.c
>> > b/drivers/gpu/drm/i915/intel_psr.c
>> > index c3abae4..68bc405 100644
>> > --- a/drivers/gpu/drm/i915/intel_psr.c
>> > +++ b/drivers/gpu/drm/i915/intel_psr.c
>> > @@ -798,6 +798,8 @@ void intel_psr_init(struct drm_device *dev)
>> >                 /* For new platforms let's respect VBT back again */
>> >                 dev_priv->psr.link_standby =
>> > dev_priv->vbt.psr.full_link;
>> > 
>> > +       DRM_ERROR("PSR: VBT recommends link_standby %d, using %d\n",
>> > dev_priv->vbt.psr.full_link, dev_priv->psr.link_standby);
>> > +
>> >         /* Override link_standby x link_off defaults */
>> >         if (i915.enable_psr == 2 && !dev_priv->psr.link_standby) {
>> >                 DRM_DEBUG_KMS("PSR: Forcing link standby\n");
>> >   
>> 
>> I applied your patch and booted with enable_psr=-1
>> 
>> [    0.763651] [drm:intel_psr_init] *ERROR* PSR: VBT recommends link_standby 0, using 0

-- 
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-04-28  8:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 21:46 i915: screen flicker Mihai Donțu
2016-04-27  7:09 ` Jani Nikula
2016-04-27 10:07   ` Mihai Donțu
2016-04-27 10:35     ` Jani Nikula
2016-04-27 15:28       ` Rodrigo Vivi
2016-04-27 17:36         ` Mihai Donțu
2016-04-27 17:42           ` Mihai Donțu
2016-04-28  8:02             ` Jani Nikula [this message]

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=87mvoei2ka.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=dhinakaran.pandiyan@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mihai.dontu@gmail.com \
    --cc=rodrigo.vivi@gmail.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