From: "Souza, Jose" <jose.souza@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915/icl: don't set CNL_DDI_CLOCk_REG_ACCESS_ON anymore
Date: Thu, 26 Jul 2018 21:02:38 +0000 [thread overview]
Message-ID: <bb88ea4fdce2c89c6d2907bcd362d5234a9bd130.camel@intel.com> (raw)
In-Reply-To: <20180726001229.13791-1-paulo.r.zanoni@intel.com>
On Wed, 2018-07-25 at 17:12 -0700, Paulo Zanoni wrote:
> The new recommendation from the spec is to simply not set this bit
> anymore. Not setting the bit would prevent some hangs that our driver
> manages to avoid since commit c8af5274c3cb ("drm/i915: enable the
> pipe/transcoder/planes later on HSW+"), and the theoretical downside
> of not setting the bit doesn't seem realistic according to the HW
> team. Let's follow their recommendation.
>
> BSpec: 20233
> References: commit c8af5274c3cb ("drm/i915: enable the
> pipe/transcoder/planes later on HSW+")
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Also another steps were removed from initialization too, the previous
step 4 and parts of step 3 but if we really need to remove it we can do
it another patch.
Reviewed-by: José Roberto de Souza <jose.souza@intel.com>
> ---
> drivers/gpu/drm/i915/intel_runtime_pm.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_runtime_pm.c
> b/drivers/gpu/drm/i915/intel_runtime_pm.c
> index 6b5aa3b074ec..cf89141b2281 100644
> --- a/drivers/gpu/drm/i915/intel_runtime_pm.c
> +++ b/drivers/gpu/drm/i915/intel_runtime_pm.c
> @@ -3372,10 +3372,6 @@ static void icl_display_core_init(struct
> drm_i915_private *dev_priv,
>
> /* 7. Setup MBUS. */
> icl_mbus_init(dev_priv);
> -
> - /* 8. CHICKEN_DCPR_1 */
> - I915_WRITE(GEN8_CHICKEN_DCPR_1, I915_READ(GEN8_CHICKEN_DCPR_1)
> |
> - CNL_DDI_CLOCK_REG_ACCESS_ON);
> }
>
> static void icl_display_core_uninit(struct drm_i915_private
> *dev_priv)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-07-26 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 0:12 [PATCH] drm/i915/icl: don't set CNL_DDI_CLOCk_REG_ACCESS_ON anymore Paulo Zanoni
2018-07-26 0:49 ` ✗ Fi.CI.BAT: failure for " Patchwork
2018-07-26 21:02 ` Souza, Jose [this message]
2018-07-27 22:06 ` [PATCH] " Paulo Zanoni
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=bb88ea4fdce2c89c6d2907bcd362d5234a9bd130.camel@intel.com \
--to=jose.souza@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@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 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).