From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: "Robert M. Fosha" <robert.m.fosha@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: Add whitelist workarounds for CFL
Date: Fri, 14 Jun 2019 07:54:48 +0100 [thread overview]
Message-ID: <9988d388-9b53-eb75-ffb5-890baf5c8c3b@linux.intel.com> (raw)
In-Reply-To: <20190614002838.3072-4-robert.m.fosha@intel.com>
On 14/06/2019 01:28, Robert M. Fosha wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Updated whitelist table for CFL.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> Signed-off-by: Robert M. Fosha <robert.m.fosha@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 35 ++++++++++++++++++++-
> 1 file changed, 34 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> index 5308a0864e78..60bd515edaf1 100644
> --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
> +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
> @@ -1092,10 +1092,43 @@ static void glk_whitelist_build(struct intel_engine_cs *engine)
>
> static void cfl_whitelist_build(struct intel_engine_cs *engine)
> {
> + struct i915_wa_list *w = &engine->whitelist;
> +
> if (engine->class != RENDER_CLASS)
> return;
>
> - gen9_whitelist_build(&engine->whitelist);
> + /* Whitelist entries from BSpec page 53688: */
> + gen9_whitelist_build(w);
> +
> + /* WaSendPushConstantsFromMMIO:cfl */
> + whitelist_reg_ext(w, COMMON_SLICE_CHICKEN2,
> + RING_FORCE_TO_NONPRIV_RW);
> +
> + /* GEN9_CS_DEBUG_MODE1 */
> + whitelist_reg_ext(w, GEN9_CS_DEBUG_MODE1,
> + RING_FORCE_TO_NONPRIV_RW);
> +
> + /* WaAllowUmdWriteTRTTRootTable:cfl */
> + whitelist_reg_ext(w, _MMIO(0x4DE0), RING_FORCE_TO_NONPRIV_RW);
> + whitelist_reg_ext(w, _MMIO(0x4DE4), RING_FORCE_TO_NONPRIV_RW);
> +
> + /* WaAllowUMDToDisableVFAutoStrip:cfl */
> + whitelist_reg_ext(w, _MMIO(0x83A8), RING_FORCE_TO_NONPRIV_RW);
> +
> + /* WaAllowPMDepthAndInvocationCountAccessFromUMD:cfl
> + * NB: this also pulls in CL_PRIMITIVES_COUNT in same block
> + * as PS_INVOCATIONS_COUNT. Likewise, TIMESTAMP in the
> + * PS_DEPTH_COUNT block.
> + */
Nitpick but please use multi-line comments in style:
/*
*
*/
We are trying not to add more of the unpopular style.
> + whitelist_reg_ext(w, CL_PRIMITIVES_COUNT,
> + RING_FORCE_TO_NONPRIV_RW |
> + RING_FORCE_TO_NONPRIV_RANGE_4);
> + whitelist_reg_ext(w, PS_DEPTH_COUNT, RING_FORCE_TO_NONPRIV_RW |
> + RING_FORCE_TO_NONPRIV_RANGE_4);
> +
> + /* WaAllowUMDAccesstoOARegisters:cfl */
> + whitelist_reg_ext(w, _MMIO(0x28A0), RING_FORCE_TO_NONPRIV_RW);
> + whitelist_reg_ext(w, OAREPORTTRIG6, RING_FORCE_TO_NONPRIV_RW);
AFAICS majority of the register here shouldn't use the whitelist_reg_ext
but normal whitelist_reg. It will help with readability a bit and the
special ones would stick out more.
> }
>
> static void cnl_whitelist_build(struct intel_engine_cs *engine)
>
With the two tweaks:
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-14 6:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 0:28 [PATCH 0/4] Update whitelist support for new hardware Robert M. Fosha
2019-06-14 0:28 ` [PATCH 1/4] drm/i915: Support flags in whitlist WAs Robert M. Fosha
2019-06-14 6:48 ` Tvrtko Ursulin
2019-06-18 1:13 ` John Harrison
2019-06-18 6:51 ` Tvrtko Ursulin
2019-06-14 0:28 ` [PATCH 2/4] drm/i915: Support whitelist workarounds on all engines Robert M. Fosha
2019-06-14 6:50 ` Tvrtko Ursulin
2019-06-14 0:28 ` [PATCH 3/4] drm/i915: Add whitelist workarounds for CFL Robert M. Fosha
2019-06-14 6:54 ` Tvrtko Ursulin [this message]
2019-06-14 0:28 ` [PATCH 4/4] drm/i915: Add whitelist workarounds for ICL Robert M. Fosha
2019-06-14 6:57 ` Tvrtko Ursulin
2019-06-14 1:09 ` ✗ Fi.CI.CHECKPATCH: warning for Update whitelist support for new hardware Patchwork
2019-06-14 14:23 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-06-14 17:19 ` Tvrtko Ursulin
2019-06-14 18:17 ` John Harrison
2019-06-14 18:22 ` Chris Wilson
2019-06-14 18:44 ` Tvrtko Ursulin
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=9988d388-9b53-eb75-ffb5-890baf5c8c3b@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=robert.m.fosha@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.