mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thakkar, Devarsh" <devarsht@ti.com>
To: "Brnich, Brandon" <b-brnich@ti.com>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"hverkuil@kernel.org" <hverkuil@kernel.org>,
	"nicolas.dufresne@collabora.com" <nicolas.dufresne@collabora.com>,
	"benjamin.gaignard@collabora.com"
	<benjamin.gaignard@collabora.com>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v6 2/4] media: imagination: e5010: Fix clk never enabled without CONFIG_PM
Date: Fri, 6 Nov 2026 14:57:37 +0000	[thread overview]
Message-ID: <b7a862f9-ffd0-41e6-a0e4-d160ebdc03a0@ti.com> (raw)
In-Reply-To: <20261023144618.1652390-3-b-brnich@ti.com>

Hi Brandon,

On 23/10/26 20:16, Brnich, Brandon wrote:
> From: Brandon Brnich <b-brnich@ti.com>
> 
> clk_prepare_enable is not called anywhere unless CONFIG_PM is set. This
> means without CONFIG_PM, the JPEG Encoder will not function properly.
> 
> Add this call during the probe sequence to properly configure the device.
> If video_registration fails after clk is enabled, clk would be left on.
> Make a label to cover this case.
> 
> Fixes: a1e294045885 ("media: imagination: Add E5010 JPEG Encoder driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Brandon Brnich <b-brnich@ti.com>
> ---
>  .../media/platform/imagination/e5010-jpeg-enc.c | 17 ++++++++++++++++-
>  1 file changed, 16 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/media/platform/imagination/e5010-jpeg-enc.c b/drivers/media/platform/imagination/e5010-jpeg-enc.c
> index 23d06709a6929..b8e24f816648d 100644
> --- a/drivers/media/platform/imagination/e5010-jpeg-enc.c
> +++ b/drivers/media/platform/imagination/e5010-jpeg-enc.c
> @@ -1101,10 +1101,18 @@ static int e5010_probe(struct platform_device *pdev)
>  
>  	pm_runtime_enable(dev);
>  
> +	if (!pm_runtime_enabled(dev)) {
> +		ret = clk_prepare_enable(e5010->clk);
> +		if (ret) {
> +			dev_err_probe(dev, ret, "failed to enable clock\n");
> +			goto fail_after_v4l2_m2m_init;
> +		}
> +	}
> +
>  	ret = video_register_device(e5010->vdev, VFL_TYPE_VIDEO, 0);
>  	if (ret) {
>  		dev_err_probe(dev, ret, "failed to register video device\n");
> -		goto fail_after_v4l2_m2m_init;
> +		goto fail_after_clock_enable;
>  	}
>  
>  	v4l2_info(&e5010->v4l2_dev, "Device registered as /dev/video%d\n",
> @@ -1112,6 +1120,11 @@ static int e5010_probe(struct platform_device *pdev)
>  
>  	return 0;
>  
> +fail_after_clock_enable:
> +	if (pm_runtime_enabled(dev))
> +		pm_runtime_disable(dev);
> +	else
> +		clk_disable_unprepare(e5010->clk);
>  fail_after_v4l2_m2m_init:
>  	v4l2_m2m_release(e5010->m2m_dev);
>  fail_after_v4l2_register:
> @@ -1126,6 +1139,8 @@ static void e5010_remove(struct platform_device *pdev)
>  	struct e5010_dev *e5010 = platform_get_drvdata(pdev);
>  
>  	pm_runtime_disable(e5010->dev);
> +	if (!pm_runtime_status_suspended(&pdev->dev))
> +		clk_disable_unprepare(e5010->clk);

I think better to disable clocks after the video device is unregistered.

Regards
Devarsh

>  	video_unregister_device(e5010->vdev);
>  	v4l2_m2m_release(e5010->m2m_dev);
>  	v4l2_device_unregister(&e5010->v4l2_dev);


  reply	other threads:[~2026-11-06 14:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 14:46 [PATCH v6 0/4] E5010 Probe Cleanup and Adding autosuspend b-brnich
2026-10-23 14:46 ` [PATCH v6 1/4] media: imagination: e5010: release m2m device on probe failure b-brnich
2026-11-06  7:27   ` Thakkar, Devarsh
2026-10-23 14:46 ` [PATCH v6 2/4] media: imagination: e5010: Fix clk never enabled without CONFIG_PM b-brnich
2026-11-06 14:57   ` Thakkar, Devarsh [this message]
2026-10-23 14:46 ` [PATCH v6 3/4] media: imagination: e5010: Move e5010_init_device to Runtime Resume Hook b-brnich
2026-10-23 14:46 ` [PATCH v6 4/4] media: imagination: e5010: Enable autosuspend for runtime PM b-brnich

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=b7a862f9-ffd0-41e6-a0e4-d160ebdc03a0@ti.com \
    --to=devarsht@ti.com \
    --cc=b-brnich@ti.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=hverkuil@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas.dufresne@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®