All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: Ce Sun <cesun102@amd.com>, amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH] amdgpu/psp: Adjust usleep_range in fence wait
Date: Tue, 10 Feb 2026 14:54:08 +0530	[thread overview]
Message-ID: <d612b935-2f85-4acb-ae72-93a62975eb9a@amd.com> (raw)
In-Reply-To: <20260210080803.3018126-1-cesun102@amd.com>



On 10-Feb-26 1:38 PM, Ce Sun wrote:
> Tune the sleep interval in the PSP fence wait loop from 10-100us to 60-100us.
> This adjustment results in an overall wait window of 1.2s (60us * 20000 iterations)
> to 2 seconds (100us * 20000 iterations), which guarantees that we can retrieve
> the correct fence value
> 
> Signed-off-by: Ce Sun <cesun102@amd.com>

Reviewed-by: Lijo Lazar <lijo.lazar@amd.com>

Thanks,
Lijo

> ---
>   drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c
> index b0540b009e84..5eeea965032a 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_psp.c
> @@ -735,7 +735,7 @@ psp_cmd_submit_buf(struct psp_context *psp,
>   		ras_intr = amdgpu_ras_intr_triggered();
>   		if (ras_intr)
>   			break;
> -		usleep_range(10, 100);
> +		usleep_range(60, 100);
>   		amdgpu_device_invalidate_hdp(psp->adev, NULL);
>   	}
>   


  reply	other threads:[~2026-02-10  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10  8:08 [PATCH] amdgpu/psp: Adjust usleep_range in fence wait Ce Sun
2026-02-10  9:24 ` Lazar, Lijo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-02-10  7:52 Ce Sun
2026-02-10  8:05 ` Sun, Ce(Overlord)

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=d612b935-2f85-4acb-ae72-93a62975eb9a@amd.com \
    --to=lijo.lazar@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=cesun102@amd.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.