From: acelan.kao@canonical.com
To: Anshuman Gupta <anshuman.gupta@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [v2] drm/i915: Tweaked Wa_14010685332 for all PCHs
Date: Wed, 30 Jun 2021 19:19:04 +0800 [thread overview]
Message-ID: <5830863.31r3eYUQgx@acelan-xps15-9560> (raw)
> dispcnlunit1_cp_xosc_clkreq clock observed to be active on TGL-H platform
> despite Wa_14010685332 original sequence, thus blocks entry to deeper s0ix
> state.
>
> The Tweaked Wa_14010685332 sequence fixes this issue, therefore use tweaked
> Wa_14010685332 sequence for every PCH since PCH_CNP.
>
> v2:
> - removed RKL from comment and simplified condition. [Rodrigo]
>
> Fixes: b896898c7369 ("drm/i915: Tweaked Wa_14010685332 for PCHs used on
> gen11 platforms") Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Imre Deak <imre.deak@intel.com>
> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> ---
>
> .../drm/i915/display/intel_display_power.c | 16 +++++++-------
> drivers/gpu/drm/i915/i915_irq.c | 21 -------------------
> 2 files changed, 8 insertions(+), 29 deletions(-)
Hi,
I didn't see this patch shown in mainline kernel tree, nor in drm-tip,
May I know what the patch's status now?
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-06-30 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 11:19 acelan.kao [this message]
2021-06-30 11:46 ` [Intel-gfx] [v2] drm/i915: Tweaked Wa_14010685332 for all PCHs Gupta, Anshuman
2021-06-30 11:56 ` Anshuman Gupta
-- strict thread matches above, loose matches on Subject: below --
2021-03-25 9:32 [Intel-gfx] [PATCH] " Anshuman Gupta
2021-07-08 7:27 ` [Intel-gfx] [v2] " AceLan Kao
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=5830863.31r3eYUQgx@acelan-xps15-9560 \
--to=acelan.kao@canonical.com \
--cc=20210601100228.6064-3-anshuman.gupta@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-gfx@lists.freedesktop.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).