From: Greg KH <gregkh@linuxfoundation.org>
To: Jian-Hong Pan <jian-hong@endlessm.com>
Cc: stable@vger.kernel.org, linux@endlessm.com, hui.wang@canonical.com
Subject: Re: [PATCH stable-5.1 0/3] drm/i915: Prevent screen from flickering when the CDCLK changes
Date: Thu, 13 Jun 2019 09:52:56 +0200 [thread overview]
Message-ID: <20190613075256.GF19685@kroah.com> (raw)
In-Reply-To: <20190610060141.5377-1-jian-hong@endlessm.com>
On Mon, Jun 10, 2019 at 02:01:39PM +0800, Jian-Hong Pan wrote:
> Hi,
>
> After apply the commit "drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio
> power is enabled", it induces the screen to flicker when the CDCLK changes on
> the laptop like ASUS E406MA. [1]
>
> So, we need these commits to prevent that:
> commit 48d9f87ddd21 drm/i915: Save the old CDCLK atomic state
> commit 2b21dfbeee72 drm/i915: Remove redundant store of logical CDCLK state
> commit 59f9e9cab3a1 drm/i915: Skip modeset for cdclk changes if possible
>
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=203623#c12
>
> Jian-Hong Pan
>
> Imre Deak (2):
> drm/i915: Save the old CDCLK atomic state
> drm/i915: Remove redundant store of logical CDCLK state
>
> Ville Syrjälä (1):
> drm/i915: Skip modeset for cdclk changes if possible
>
> drivers/gpu/drm/i915/i915_drv.h | 3 +-
> drivers/gpu/drm/i915/intel_cdclk.c | 155 ++++++++++++++++++++++-----
> drivers/gpu/drm/i915/intel_display.c | 48 +++++++--
> drivers/gpu/drm/i915/intel_drv.h | 18 +++-
> 4 files changed, 186 insertions(+), 38 deletions(-)
These are all big patches, I would like to get an ack from the i915
developer(s) that these are acceptable for the stable tree before
applying them...
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-13 16:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 10:09 [PATCH 5.1 stable v2] drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio power is enabled Jian-Hong Pan
2019-06-10 6:01 ` [PATCH stable-5.1 0/3] drm/i915: Prevent screen from flickering when the CDCLK changes Jian-Hong Pan
2019-06-13 7:52 ` Greg KH [this message]
2019-06-13 8:37 ` Jian-Hong Pan
2019-06-13 10:05 ` Ville Syrjälä
2019-06-14 5:59 ` Jian-Hong Pan
2019-06-14 14:11 ` Ville Syrjälä
2019-06-10 6:01 ` [PATCH stable-5.1 1/3] drm/i915: Save the old CDCLK atomic state Jian-Hong Pan
2019-06-20 14:19 ` Greg KH
2019-06-21 10:07 ` [PATCH stable-5.1 v2 0/4] drm/i915: Prevent screen from flickering when the CDCLK changes Jian-Hong Pan
2019-06-21 10:07 ` [PATCH stable-5.1 v2 1/4] drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio power is enabled Jian-Hong Pan
2019-06-21 10:07 ` [PATCH stable-5.1 v2 2/4] drm/i915: Save the old CDCLK atomic state Jian-Hong Pan
2019-06-21 10:07 ` [PATCH stable-5.1 v2 3/4] drm/i915: Remove redundant store of logical CDCLK state Jian-Hong Pan
2019-06-21 10:07 ` [PATCH stable-5.1 v2 4/4] drm/i915: Skip modeset for cdclk changes if possible Jian-Hong Pan
2019-07-01 15:14 ` [PATCH stable-5.1 v2 0/4] drm/i915: Prevent screen from flickering when the CDCLK changes Greg KH
2019-06-10 6:01 ` [PATCH stable-5.1 2/3] drm/i915: Remove redundant store of logical CDCLK state Jian-Hong Pan
2019-06-10 6:01 ` [PATCH stable-5.1 3/3] drm/i915: Skip modeset for cdclk changes if possible Jian-Hong Pan
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=20190613075256.GF19685@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hui.wang@canonical.com \
--cc=jian-hong@endlessm.com \
--cc=linux@endlessm.com \
--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;
as well as URLs for NNTP newsgroup(s).