Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sultan Alsawaf <sultan@kerneltoast.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/i915: Disable Panel Self Refresh (PSR) by default
Date: Mon, 30 Mar 2020 08:50:23 -0700	[thread overview]
Message-ID: <20200330155023.GA2022@sultan-box.localdomain> (raw)
In-Reply-To: <20200330085104.GB239298@kroah.com>

On Mon, Mar 30, 2020 at 10:51:04AM +0200, Greg KH wrote:
> On Sun, Mar 29, 2020 at 08:30:56PM -0700, Sultan Alsawaf wrote:
> > From: Sultan Alsawaf <sultan@kerneltoast.com>
> > 
> > On all Dell laptops with panels and chipsets that support PSR (an
> > esoteric power-saving mechanism), both PSR1 and PSR2 cause flickering
> > and graphical glitches, sometimes to the point of making the laptop
> > unusable. Many laptops don't support PSR so it isn't known if PSR works
> > correctly on any consumer hardware as of 5.4. PSR was enabled by default
> > in 5.0 for capable hardware, so this patch just restores the previous
> > functionality of PSR being disabled by default.
> > 
> > More info is available on the freedesktop bug:
> > https://gitlab.freedesktop.org/drm/intel/issues/425
> > 
> > Cc: <stable@vger.kernel.org> # 5.4.x
> > Signed-off-by: Sultan Alsawaf <sultan@kerneltoast.com>
> > ---
> >  drivers/gpu/drm/i915/i915_params.c | 3 +--
> >  drivers/gpu/drm/i915/i915_params.h | 2 +-
> >  2 files changed, 2 insertions(+), 3 deletions(-)
> 
> What is the git commit id of this patch in Linus's tree?
> 
> thanks,
> 
> greg k-h

This isn't in Linus' tree. I know for a fact that 5.4 has broken PSR support
that'll never be fixed, but I wasn't sure if PSR was still broken in 5.6.

However, I tested 5.6 for a bit right now and PSR is still broken. And to top it
off, I managed to reproduce some PSR glitches with the drm-tip branch, so
there's currently no kernel in existence with functional PSR. :)

I will send this patch for inclusion in Linus' tree, so please disregard it for
now.

Thanks,
Sultan

  reply	other threads:[~2020-03-30 15:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30  3:30 [PATCH 0/2] A couple of important fixes for i915 on 5.4 Sultan Alsawaf
2020-03-30  3:30 ` [PATCH 1/2] drm/i915: Disable Panel Self Refresh (PSR) by default Sultan Alsawaf
2020-03-30  8:51   ` Greg KH
2020-03-30 15:50     ` Sultan Alsawaf [this message]
2020-03-30  3:30 ` [PATCH 2/2] drm/i915/gt: Schedule request retirement when timeline idles Sultan Alsawaf
2020-03-30 15:56   ` Sultan Alsawaf
2020-03-30 16:27   ` Chris Wilson
2020-03-30 16:35     ` Sultan Alsawaf
2020-03-30 16:45       ` Chris Wilson
2020-04-07 20:28         ` Sultan Alsawaf
2020-04-07 20:43           ` [PATCH v2] " Sultan Alsawaf
2020-04-12  7:48             ` Sultan Alsawaf
2020-04-12  7:56               ` Greg KH
2020-04-13 14:37                 ` Salvatore Bonaccorso
2020-04-13 15:23                 ` Sultan Alsawaf
2020-04-13 15:29                   ` [PATCH v3] " Sultan Alsawaf
2020-04-17  9:38                     ` Sultan Alsawaf
2020-04-18 10:29                       ` Greg KH
2020-04-18 10:30                     ` Greg KH
2020-03-30  8:51 ` [PATCH 0/2] A couple of important fixes for i915 on 5.4 Greg KH

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=20200330155023.GA2022@sultan-box.localdomain \
    --to=sultan@kerneltoast.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@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