Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andrzej Hajda <andrzej.hajda@intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>, intel-gfx@lists.freedesktop.org
Cc: matthew.auld@intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/selftests: Remove hardcoded value with a macro
Date: Tue, 13 Dec 2022 15:14:43 +0100	[thread overview]
Message-ID: <2b8b1fdd-8dfb-797e-640c-425f72ccfbc8@intel.com> (raw)
In-Reply-To: <20221213120010.5857-1-nirmoy.das@intel.com>



On 13.12.2022 13:00, Nirmoy Das wrote:
> Use MI_USE_GGTT instead of hardcoded value.
>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
> ---
>   drivers/gpu/drm/i915/gem/selftests/i915_gem_coherency.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/selftests/i915_gem_coherency.c b/drivers/gpu/drm/i915/gem/selftests/i915_gem_coherency.c
> index c228fe4aba50..3bef1beec7cb 100644
> --- a/drivers/gpu/drm/i915/gem/selftests/i915_gem_coherency.c
> +++ b/drivers/gpu/drm/i915/gem/selftests/i915_gem_coherency.c
> @@ -222,7 +222,7 @@ static int gpu_set(struct context *ctx, unsigned long offset, u32 v)
>   	}
>   
>   	if (GRAPHICS_VER(ctx->engine->i915) >= 8) {
> -		*cs++ = MI_STORE_DWORD_IMM_GEN4 | 1 << 22;
> +		*cs++ = MI_STORE_DWORD_IMM_GEN4 | MI_USE_GGTT;

Reviewed-by: Andrzej Hajda <andrzej.hajda@intel.com>

Regards
Andrzej

>   		*cs++ = lower_32_bits(i915_ggtt_offset(vma) + offset);
>   		*cs++ = upper_32_bits(i915_ggtt_offset(vma) + offset);
>   		*cs++ = v;


      parent reply	other threads:[~2022-12-13 14:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 12:00 [Intel-gfx] [PATCH] drm/i915/selftests: Remove hardcoded value with a macro Nirmoy Das
2022-12-13 12:17 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2022-12-13 12:38 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-12-15 11:17   ` Das, Nirmoy
2022-12-13 13:04 ` [Intel-gfx] [PATCH] " Matthew Auld
2022-12-13 14:14 ` Andrzej Hajda [this message]

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=2b8b1fdd-8dfb-797e-640c-425f72ccfbc8@intel.com \
    --to=andrzej.hajda@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=nirmoy.das@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