From: Kendall Willis <k-willis@ti.com>
To: "Lannynd, Thorsten" <t-lannynd@ti.com>
Cc: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Brnich, Brandon" <b-brnich@ti.com>,
"Etheridge, Darren" <detheridge@ti.com>,
"Nas Chung" <nas.chung@chipsnmedia.com>,
Jackson Lee <jackson.lee@chipsnmedia.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: chips-media: wave5: Add system suspend/resume support
Date: Wed, 8 Jul 2026 11:22:30 -0500 [thread overview]
Message-ID: <20260708162230.slp2nh6itapd5azl@uda0506412> (raw)
In-Reply-To: <1c4ad376a72b4e92965620d94c995360@ti.com>
On 11:12-20260708, Lannynd, Thorsten wrote:
> Hi Kendall,
> On 07/08/2026 3:23 PM, Kendall Willis wrote:
> > Hi Thorsten,
> > On 15:16-20260707, Thorsten Lannynd wrote:
> > > Add SET_SYSTEM_SLEEP_PM_OPS with wave5_system_suspend() and
> > > wave5_system_resume() so the driver handles system suspend to RAM.
> > > When suspended, Wave5 should gracefully finish the job and shutdown.
> > > When resumed, Wave5 should resume the context and finish executing the
> > > suspended stream.
> > >
> > > Signed-off-by: Thorsten Lannynd <t-lannynd@ti.com>
> > > ---
> > > .../platform/chips-media/wave5/wave5-vpu.c | 30 +++++++++++++++++++
> > > 1 file changed, 30 insertions(+)
> > >
> > > diff --git a/drivers/media/platform/chips-media/wave5/wave5-vpu.c
> > > b/drivers/media/platform/chips-media/wave5/wave5-vpu.c
> > > index 76d57c6b6..a83640751 100644
> > > --- a/drivers/media/platform/chips-media/wave5/wave5-vpu.c
> > > +++ b/drivers/media/platform/chips-media/wave5/wave5-vpu.c
> > > @@ -254,7 +254,37 @@ static __maybe_unused int
> > wave5_pm_resume(struct device *dev)
> > > return ret;
> > > }
> > >
> > > +static __maybe_unused int wave5_system_suspend(struct device *dev) {
> > > + struct vpu_device *vpu = dev_get_drvdata(dev);
> > > +
> > > + if (vpu->v4l2_m2m_dec_dev)
> > > + v4l2_m2m_suspend(vpu->v4l2_m2m_dec_dev);
> > > + if (vpu->v4l2_m2m_enc_dev)
> > > + v4l2_m2m_suspend(vpu->v4l2_m2m_enc_dev);
> > > +
> > > + return pm_runtime_force_suspend(dev); }
> > > +
> > > +static __maybe_unused int wave5_system_resume(struct device *dev) {
> > > + struct vpu_device *vpu = dev_get_drvdata(dev);
> > > + int ret;
> > > +
> > > + ret = pm_runtime_force_resume(dev);
> > > + if (ret < 0)
> > > + return ret;
> > > +
> > > + if (vpu->v4l2_m2m_dec_dev)
> > > + v4l2_m2m_resume(vpu->v4l2_m2m_dec_dev);
> > > + if (vpu->v4l2_m2m_enc_dev)
> > > + v4l2_m2m_resume(vpu->v4l2_m2m_enc_dev);
> >
> > Can you confirm that v4l2_m2m_dec_dev can be resumed before
> > v4l2_m2m_enc_dev? Usually you would suspend devices and resume them in
> > the opposite order so that you can preserve dependencies.
> Yes, both devices share the same IP and suspend/resume hooks, so the ordering
> should not matter.
Thanks for checking on this.
Reviewed-by: Kendall Willis <k-willis@ti.com>
>
> Thanks,
> Thorsten
> > Best,
> > Kendall
> >
> > > +
> > > + return 0;
> > > +}
> > > +
> > > static const struct dev_pm_ops wave5_pm_ops = {
> > > + SET_SYSTEM_SLEEP_PM_OPS(wave5_system_suspend,
> > wave5_system_resume)
> > > SET_RUNTIME_PM_OPS(wave5_pm_suspend, wave5_pm_resume,
> > NULL) };
> > >
> > > --
> > > 2.34.1
> > >
next prev parent reply other threads:[~2026-07-08 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 20:16 [PATCH] media: chips-media: wave5: Add system suspend/resume support Thorsten Lannynd
2026-07-08 15:23 ` Kendall Willis
2026-07-08 16:12 ` Lannynd, Thorsten
2026-07-08 16:22 ` Kendall Willis [this message]
2026-09-09 3:57 ` jackson.lee
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=20260708162230.slp2nh6itapd5azl@uda0506412 \
--to=k-willis@ti.com \
--cc=b-brnich@ti.com \
--cc=detheridge@ti.com \
--cc=jackson.lee@chipsnmedia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nas.chung@chipsnmedia.com \
--cc=t-lannynd@ti.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