AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sultan Alsawaf <sultan@kerneltoast.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: amd-gfx@lists.freedesktop.org, Peyton.Lee@amd.com
Subject: Re: [PATCH v2] drm/amd: Check that VPE has reached DPM0 in idle handler
Date: Fri, 10 Oct 2025 23:54:33 -0700	[thread overview]
Message-ID: <aOn_KQXm2uPDZkWu@sultan-box> (raw)
In-Reply-To: <20251011003723.209074-1-mario.limonciello@amd.com>

Hi Mario,

On Fri, Oct 10, 2025 at 07:37:22PM -0500, Mario Limonciello wrote:
> [Why]
> Newer VPE microcode has functionality that will decrease DPM level
> only when a workload has run for 2 or more seconds.  If VPE is turned
> off before this DPM decrease, the SOC can get stuck with a higher
> DPM level.
> 
> This can happen from amdgpu's ring buffer test because it's a short
> quick workload for VPE and VPE is turned off after 1s.
> 
> [How]
> In idle handler besides checking fences are drained check that VPE DPM
> level is really is at DPM0. If not, schedule delayed work again until
> it is.
> 
> Cc: Peyton.Lee@amd.com
> Reported-by: Sultan Alsawaf <sultan@kerneltoast.com>
> Closes: https://gitlab.freedesktop.org/drm/amd/-/issues/4615
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> Drop unnecessary spurious dpm_level variable
>  drivers/gpu/drm/amd/amdgpu/amdgpu_vpe.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vpe.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vpe.c
> index 474bfe36c0c2..9065d799c2c4 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_vpe.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_vpe.c
> @@ -326,11 +326,16 @@ static void vpe_idle_work_handler(struct work_struct *work)
>  {
>  	struct amdgpu_device *adev =
>  		container_of(work, struct amdgpu_device, vpe.idle_work.work);
> +	struct amdgpu_vpe *vpe = &adev->vpe;
>  	unsigned int fences = 0;
> +	uint32_t dpm_level;
>  
>  	fences += amdgpu_fence_count_emitted(&adev->vpe.ring);
>  
> -	if (fences == 0)
> +	dpm_level = adev->pm.dpm_enabled ?
> +		    RREG32(vpe_get_reg_offset(vpe, 0, vpe->regs.dpm_request_lv)) : 0;

This register read can be skipped when fences != 0. Perhaps with a goto label?

> +
> +	if (fences == 0 && dpm_level == 0)
>  		amdgpu_device_ip_set_powergating_state(adev, AMD_IP_BLOCK_TYPE_VPE, AMD_PG_STATE_GATE);
>  	else
>  		schedule_delayed_work(&adev->vpe.idle_work, VPE_IDLE_TIMEOUT);
> -- 
> 2.51.0
> 

Sultan

      reply	other threads:[~2025-10-11  8:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-11  0:37 [PATCH v2] drm/amd: Check that VPE has reached DPM0 in idle handler Mario Limonciello
2025-10-11  6:54 ` Sultan Alsawaf [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=aOn_KQXm2uPDZkWu@sultan-box \
    --to=sultan@kerneltoast.com \
    --cc=Peyton.Lee@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=mario.limonciello@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox