From: Brandon Brnich <b-brnich@ti.com>
To: <devarsht@ti.com>, <mchehab@kernel.org>, <hverkuil@kernel.org>,
<sebastian.fricke@collabora.com>,
<benjamin.gaignard@collabora.com>, <linux-media@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: Brandon Brnich <b-brnich@ti.com>, <stable@vger.kernel.org>
Subject: [PATCH v4 2/4] media: imagination: e5010: Fix clk never enabled without CONFIG_PM
Date: Mon, 31 Aug 2026 16:32:29 -0500 [thread overview]
Message-ID: <20260831213231.2125544-3-b-brnich@ti.com> (raw)
In-Reply-To: <20260831213231.2125544-1-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 | 14 ++++++++++++--
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/drivers/media/platform/imagination/e5010-jpeg-enc.c b/drivers/media/platform/imagination/e5010-jpeg-enc.c
index d3c11337c815d..e98fcd3fcd9ae 100644
--- a/drivers/media/platform/imagination/e5010-jpeg-enc.c
+++ b/drivers/media/platform/imagination/e5010-jpeg-enc.c
@@ -1099,19 +1099,28 @@ static int e5010_probe(struct platform_device *pdev)
goto fail_after_video_register_device;
}
- pm_runtime_enable(dev);
+ ret = clk_prepare_enable(e5010->clk);
+ if (ret) {
+ dev_err_probe(dev, ret, "failed to enable clock\n");
+ goto fail_after_video_register_device;
+ }
+
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_video_register_device;
+ goto fail_after_clock_enable;
}
+ pm_runtime_enable(dev);
+
v4l2_info(&e5010->v4l2_dev, "Device registered as /dev/video%d\n",
e5010->vdev->num);
return 0;
+fail_after_clock_enable:
+ clk_disable_unprepare(e5010->clk);
fail_after_video_register_device:
v4l2_m2m_release(e5010->m2m_dev);
fail_after_v4l2_register:
@@ -1126,6 +1135,7 @@ static void e5010_remove(struct platform_device *pdev)
struct e5010_dev *e5010 = platform_get_drvdata(pdev);
pm_runtime_disable(e5010->dev);
+ clk_disable_unprepare(e5010->clk);
video_unregister_device(e5010->vdev);
v4l2_m2m_release(e5010->m2m_dev);
v4l2_device_unregister(&e5010->v4l2_dev);
--
2.43.0
next prev parent reply other threads:[~2026-08-31 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 21:32 [PATCH v4 0/4] E5010 Probe Cleanup and Adding autosuspend Brandon Brnich
2026-08-31 21:32 ` [PATCH v4 1/4] media: imagination: e5010: Properly Release m2m_dev if probe fails Brandon Brnich
2026-08-31 21:32 ` Brandon Brnich [this message]
2026-08-31 21:32 ` [PATCH v4 3/4] media: imagination: e5010: Move e5010_init_device to Runtime Resume Hook Brandon Brnich
2026-08-31 21:32 ` [PATCH v4 4/4] media: imagination: e5010: Enable autosuspend for runtime PM Brandon 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=20260831213231.2125544-3-b-brnich@ti.com \
--to=b-brnich@ti.com \
--cc=benjamin.gaignard@collabora.com \
--cc=devarsht@ti.com \
--cc=hverkuil@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--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