From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] Revert "drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk"
Date: Thu, 07 Dec 2017 16:58:52 +0200 [thread overview]
Message-ID: <1512658732.4586.40.camel@linux.intel.com> (raw)
In-Reply-To: <20171206222507.19613-1-rodrigo.vivi@intel.com>
Hi,
Thanks, this was included in the pull.
One comment below, not strictly related to this patch.
On Wed, 2017-12-06 at 14:25 -0800, Rodrigo Vivi wrote:
> From: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
>
> This reverts commit 8f067837c4b713ce2e69be95af7b2a5eb3bd7de8.
>
> HSD says "WA withdrawn. It was causing corruption with some images.
> WA is not strictly necessary since this bug just causes loss of FBC
> compression with some sizes and images, but doesn't break anything."
>
> Fixes: 8f067837c4b7 ("drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk")
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Radhakrishna Sripada <radhakrishna.sripada@intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Link: https://patchwork.freedesktop.org/patch/msgid/20171117010825.23118-1-radhakrishna.sripada@intel.com
> (cherry picked from commit 0cfecb7c4b9b45ed1776162e132b43f92564f3f4)
<SNIP>
> +++ b/drivers/gpu/drm/i915/intel_pm.c
> @@ -124,7 +124,6 @@ static void bxt_init_clock_gating(struct drm_i915_private *dev_priv)
>
> static void glk_init_clock_gating(struct drm_i915_private *dev_priv)
> {
> - u32 val;
This resulted being a pain because it got reused by another upstream
patch, so while this revert removed the variable, the newly added non-
conflicting code still depended on it.
More specific variable names like "dpfc" and allowing compiler to
decide when to optimize and recycle variables would have helped :)
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-12-07 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-21 10:20 drm/i915 fixes that failed to backport to v4.15 Jani Nikula
2017-11-22 6:10 ` Zhenyu Wang
2017-12-06 22:25 ` [PATCH] Revert "drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk" Rodrigo Vivi
2017-12-07 14:58 ` Joonas Lahtinen [this message]
2017-12-06 22:28 ` ✗ Fi.CI.BAT: failure for Revert "drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk" (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-11-17 1:08 [PATCH] Revert "drm/i915: Display WA #1133 WaFbcSkipSegments:cnl, glk" Radhakrishna Sripada
2017-11-17 17:55 ` Rodrigo Vivi
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=1512658732.4586.40.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.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.