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: <k-willis@ti.com>, <jai.luthra@ideasonboard.com>,
<stable@vger.kernel.org>
Subject: Re: [PATCH v7 3/4] media: imagination: e5010: Update
Date: Tue, 10 Nov 2026 10:23:59 -0600 [thread overview]
Message-ID: <762a1a3d-ac18-4220-a9fd-bafcb247ee6b@ti.com> (raw)
In-Reply-To: <20261110155810.18521-4-b-brnich@ti.com>
Hi All,
Will need to resend this series because the subject got cut. Will
re-send shortly.
On 11/10/26 09:58, Brandon Brnich wrote:
> The PM framework skips the runtime resume hook if the device was never on
> in the first place. This results in a crash in the system resume hook when
> a call to e5010_init_device attempts a write to a powered down device.
>
> Move e5010_init_device to the resume hook to ensure register write only
> occurs when device is properly powered on.
>
> e5010_init_device needs to be called after e5010_reset for next
> device_run to have all registers properly reset. Without this call,
> register values are stale. Similarly, e5010_last_context_run should be
> set to NULL in e5010_init_device so the next device_run call does not
> use stale QP values.
>
> Fixes: a1e294045885 ("media: imagination: Add E5010 JPEG Encoder driver")
> Cc: stable@vger.kernel.org
> Signed-off-by: Brandon Brnich <b-brnich@ti.com>
> ---
> .../platform/imagination/e5010-jpeg-enc.c | 19 ++++++++++++-------
> 1 file changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/media/platform/imagination/e5010-jpeg-enc.c b/drivers/media/platform/imagination/e5010-jpeg-enc.c
> index 17ea616ff1795..4e77112b59197 100644
> --- a/drivers/media/platform/imagination/e5010-jpeg-enc.c
> +++ b/drivers/media/platform/imagination/e5010-jpeg-enc.c
> @@ -986,6 +986,8 @@ static int e5010_init_device(struct e5010_dev *e5010)
> {
> int ret = 0;
>
> + e5010->last_context_run = NULL;
> +
> /*TODO: Set MMU in bypass mode until support for the same is added in driver*/
> e5010_hw_bypass_mmu(e5010->mmu_base, 1);
>
> @@ -1488,7 +1490,9 @@ static void e5010_device_run(void *priv)
>
> device_busy_err:
> e5010_reset(e5010->dev, e5010->core_base, e5010->mmu_base);
> -
> + ret = e5010_init_device(e5010);
> + if (ret)
> + v4l2_err(&e5010->v4l2_dev, "failed to initialize device after reset\n");
> no_ready_buf_err:
> if (s_vb) {
> v4l2_m2m_src_buf_remove_by_buf(ctx->fh.m2m_ctx, s_vb);
> @@ -1517,6 +1521,13 @@ static int e5010_runtime_resume(struct device *dev)
> return ret;
> }
>
> + ret = e5010_init_device(e5010);
> + if (ret) {
> + dev_err(dev, "Failed to re-enable e5010 device\n");
> + clk_disable_unprepare(e5010->clk);
> + return ret;
> + }
> +
> return 0;
> }
>
> @@ -1549,12 +1560,6 @@ static int e5010_resume(struct device *dev)
> if (ret < 0)
> return ret;
>
> - ret = e5010_init_device(e5010);
> - if (ret) {
> - dev_err(dev, "Failed to re-enable e5010 device\n");
> - return ret;
> - }
> -
> v4l2_m2m_resume(e5010->m2m_dev);
>
> return ret;
next prev parent reply other threads:[~2026-11-10 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 15:58 [PATCH v7 0/4] E5010 Probe Cleanup and Adding autosuspend Brandon Brnich
2026-11-10 15:58 ` [PATCH v7 1/4] media: imagination: e5010: release m2m device on probe failure Brandon Brnich
2026-11-10 15:58 ` [PATCH v7 2/4] media: imagination: e5010: Fix clk never enabled without CONFIG_PM Brandon Brnich
2026-11-10 15:58 ` [PATCH v7 3/4] media: imagination: e5010: Update Brandon Brnich
2026-11-10 16:23 ` Brandon Brnich [this message]
2026-11-10 15:58 ` [PATCH v7 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=762a1a3d-ac18-4220-a9fd-bafcb247ee6b@ti.com \
--to=b-brnich@ti.com \
--cc=benjamin.gaignard@collabora.com \
--cc=devarsht@ti.com \
--cc=hverkuil@kernel.org \
--cc=jai.luthra@ideasonboard.com \
--cc=k-willis@ti.com \
--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
all inboxes | Powered by JetHome®