mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Linmao Li <lilinmao@kylinos.cn>,
	Nas Chung <nas.chung@chipsnmedia.com>,
	 Jackson Lee <jackson.lee@chipsnmedia.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
	Sebastian Fricke <sebastian.fricke@collabora.com>,
	Hans Verkuil <hverkuil@kernel.org>,
	 linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	 stable@vger.kernel.org
Subject: Re: [PATCH] media: chips-media: wave5: Balance runtime PM on encoder close errors
Date: Mon, 28 Sep 2026 16:57:23 -0400	[thread overview]
Message-ID: <7f06fbc16db2391baa1b0051943cfbafe961fa07.camel@collabora.com> (raw)
In-Reply-To: <20260717075714.1508938-1-lilinmao@kylinos.cn>

[-- Attachment #1: Type: text/plain, Size: 2782 bytes --]

Le vendredi 17 juillet 2026 à 15:57 +0800, Linmao Li a écrit :
> wave5_vpu_enc_close() resumes the device before taking the hardware lock.
> Its three error paths call pm_runtime_resume_and_get() again instead of
> dropping that reference.  Each failure therefore increments the runtime PM
> usage count twice and can prevent the device from suspending afterward.
> 
> Replace the extra resume calls with pm_runtime_put_sync() to balance the
> reference acquired on entry, matching the successful close path.  This
> aligns wave5_vpu_enc_close() with wave5_vpu_dec_close(), which already
> releases the reference on its error paths.
> 
> Fixes: 2092b3833487 ("media: chips-media: wave5: Support runtime suspend/resume")
> Cc: stable@vger.kernel.org
> Signed-off-by: Linmao Li <lilinmao@kylinos.cn>

Reviewed-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>

picked, ty.

> ---
>  .../platform/chips-media/wave5/wave5-vpuapi.c     | 15 +++++++--------
>  1 file changed, 7 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/media/platform/chips-media/wave5/wave5-vpuapi.c b/drivers/media/platform/chips-media/wave5/wave5-vpuapi.c
> index f77abd5e122a..4c1842f02c88 100644
> --- a/drivers/media/platform/chips-media/wave5/wave5-vpuapi.c
> +++ b/drivers/media/platform/chips-media/wave5/wave5-vpuapi.c
> @@ -754,7 +754,7 @@ int wave5_vpu_enc_close(struct vpu_instance *inst, u32 *fail_res)
>  
>  	ret = mutex_lock_interruptible(&vpu_dev->hw_lock);
>  	if (ret) {
> -		pm_runtime_resume_and_get(inst->dev->dev);
> +		pm_runtime_put_sync(inst->dev->dev);
>  		return ret;
>  	}
>  
> @@ -762,16 +762,13 @@ int wave5_vpu_enc_close(struct vpu_instance *inst, u32 *fail_res)
>  		ret = wave5_vpu_enc_finish_seq(inst, fail_res);
>  		if (ret < 0 && *fail_res != WAVE5_SYSERR_VPU_STILL_RUNNING) {
>  			dev_warn(inst->dev->dev, "enc_finish_seq timed out\n");
> -			pm_runtime_resume_and_get(inst->dev->dev);
> -			mutex_unlock(&vpu_dev->hw_lock);
> -			return ret;
> +			goto unlock_and_return;
>  		}
>  
>  		if (*fail_res == WAVE5_SYSERR_VPU_STILL_RUNNING &&
>  		    retry++ >= MAX_FIRMWARE_CALL_RETRY) {
> -			pm_runtime_resume_and_get(inst->dev->dev);
> -			mutex_unlock(&vpu_dev->hw_lock);
> -			return -ETIMEDOUT;
> +			ret = -ETIMEDOUT;
> +			goto unlock_and_return;
>  		}
>  	} while (ret != 0);
>  
> @@ -787,10 +784,12 @@ int wave5_vpu_enc_close(struct vpu_instance *inst, u32 *fail_res)
>  	}
>  
>  	wave5_vdi_free_dma_memory(vpu_dev, &p_enc_info->vb_task);
> +
> +unlock_and_return:
>  	mutex_unlock(&vpu_dev->hw_lock);
>  	pm_runtime_put_sync(inst->dev->dev);
>  
> -	return 0;
> +	return ret;
>  }
>  
>  int wave5_vpu_enc_register_frame_buffer(struct vpu_instance *inst, unsigned int num,

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-09-28 20:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  7:57 Linmao Li
2026-09-28 20:57 ` Nicolas Dufresne [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=7f06fbc16db2391baa1b0051943cfbafe961fa07.camel@collabora.com \
    --to=nicolas.dufresne@collabora.com \
    --cc=hverkuil@kernel.org \
    --cc=jackson.lee@chipsnmedia.com \
    --cc=lilinmao@kylinos.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.com \
    --cc=sebastian.fricke@collabora.com \
    --cc=stable@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®