From: Sultan Alsawaf <sultan@kerneltoast.com>
To: linux-kernel@vger.kernel.org
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Sultan Alsawaf <sultan@kerneltoast.com>
Subject: [PATCH 0/1] drm/i915: Disable Panel Self Refresh (PSR) by default
Date: Mon, 30 Mar 2020 09:30:05 -0700 [thread overview]
Message-ID: <20200330163006.4064-1-sultan@kerneltoast.com> (raw)
From: Sultan Alsawaf <sultan@kerneltoast.com>
Hi,
Laptops which support an esoteric power-saving mechanism called Panel Self
Refresh (PSR) suffer from severe graphical corruption and flickering. Enabled by
default in 5.0, PSR causes graphical corruption to the point of unusability on
many Dell laptops made within the past few years, since they typically support
PSR. A bug was filed with Intel several months ago for this with more
information [1]. I suspect most of the community hasn't been affected by this
bug because ThinkPads and many other laptops I checked didn't support PSR. As of
writing, the issues I observed with PSR are neither fully fixed in Intel's
drm-tip branch nor in 5.6. Disabling PSR by default brings us safely back to
pre-5.0 behavior, remedying the glitches. Also, Ubuntu now ships with PSR
disabled by default in its affected kernels, so there is distro support behind
this change.
Thanks,
Sultan
[1] https://gitlab.freedesktop.org/drm/intel/issues/425
Sultan Alsawaf (1):
drm/i915: Disable Panel Self Refresh (PSR) by default
drivers/gpu/drm/i915/i915_params.c | 3 +--
drivers/gpu/drm/i915/i915_params.h | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
--
2.26.0
next reply other threads:[~2020-03-30 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 16:30 Sultan Alsawaf [this message]
2020-03-30 16:30 ` [PATCH 1/1] drm/i915: Disable Panel Self Refresh (PSR) by default Sultan Alsawaf
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=20200330163006.4064-1-sultan@kerneltoast.com \
--to=sultan@kerneltoast.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@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.