From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] !fixup: drm/xe/gsc: GSC FW load
Date: Thu, 7 Dec 2023 16:53:18 -0800 [thread overview]
Message-ID: <760dfcff-cb81-4434-a03c-6ab89c9fdded@intel.com> (raw)
In-Reply-To: <20231207205556.495523-1-mika.kuoppala@linux.intel.com>
On 12/7/2023 12:55 PM, Mika Kuoppala wrote:
> Fix timeout to be in usecs for xe_mmio_wait32
>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Thanks for catching this.
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Daniele
> ---
> drivers/gpu/drm/xe/xe_gsc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gsc.c b/drivers/gpu/drm/xe/xe_gsc.c
> index 4aad6a8c9dde..a8a895cf4b44 100644
> --- a/drivers/gpu/drm/xe/xe_gsc.c
> +++ b/drivers/gpu/drm/xe/xe_gsc.c
> @@ -182,7 +182,7 @@ static int gsc_fw_wait(struct xe_gt *gt)
> return xe_mmio_wait32(gt, HECI_FWSTS1(MTL_GSC_HECI1_BASE),
> HECI1_FWSTS1_INIT_COMPLETE,
> HECI1_FWSTS1_INIT_COMPLETE,
> - 500, NULL, false);
> + 500 * USEC_PER_MSEC, NULL, false);
> }
>
> static int gsc_upload(struct xe_gsc *gsc)
next prev parent reply other threads:[~2023-12-08 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 20:55 [PATCH] !fixup: drm/xe/gsc: GSC FW load Mika Kuoppala
2023-12-08 0:53 ` Daniele Ceraolo Spurio [this message]
2023-12-08 3:23 ` ✓ CI.Patch_applied: success for " Patchwork
2023-12-08 3:23 ` ✓ CI.checkpatch: " Patchwork
2023-12-08 3:25 ` ✓ CI.KUnit: " Patchwork
2023-12-08 3:32 ` ✓ CI.Build: " Patchwork
2023-12-08 3:32 ` ✓ CI.Hooks: " Patchwork
2023-12-08 3:34 ` ✓ CI.checksparse: " Patchwork
2023-12-08 4:09 ` ✓ CI.BAT: " Patchwork
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=760dfcff-cb81-4434-a03c-6ab89c9fdded@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mika.kuoppala@linux.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