From: Kinn Coelho Juliao <kinncj@gmail.com>
To: pratap.nirujogi@amd.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Bin.Du@amd.com, mario.limonciello@amd.com,
sultan@kerneltoast.com, Kinn Coelho Juliao <kinncj@gmail.com>
Subject: Re: [PATCH] media: amd: isp4: add system suspend/resume support
Date: Tue, 3 Mar 2026 19:28:11 -0500 [thread overview]
Message-ID: <20260304002811.95497-1-kinncj@gmail.com> (raw)
In-Reply-To: <bb892e59-8fc9-4d1b-94aa-996a66392405@amd.com>
Thanks Pratap, Mario.
I reviewed commit 0288a345f19b ("drm/amdgpu/isp: fix SMU warning
during ISP suspend-resume"). I understand it marks ISP MFD children as
syscore devices and manages their suspend/resume from the amdgpu parent
via pm_runtime_force_suspend/resume.
I'm curious about one thing though; on my current system (7.0-rc1),
s2idle resume still hangs with the in-tree V4L2 module loaded. My
out-of-tree module, which adds dev_pm_ops that call
isp4sd_pwroff_and_deinit() before suspend, resolves the hang.
pm_runtime_force_suspend() manages the power domain but doesn't tear
down firmware ring buffers or V4L2 streaming state. If the camera was
active at any point during the session when suspend occurs, the driver
would have stale state on resume. That seems to be what's causing the
hang on my hardware (HP ZBook Ultra G1a, Strix Halo).
Is the firmware/streaming state teardown handled elsewhere that I'm
missing, or does the V4L2 driver still need its own suspend path?
Thanks,
Kinn
next prev parent reply other threads:[~2026-03-04 0:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 7:30 [PATCH v9 0/7] Add AMD ISP4 driver Bin Du
2026-03-02 7:30 ` [PATCH v9 1/7] media: platform: amd: Introduce amd isp4 capture driver Bin Du
2026-03-02 7:30 ` [PATCH v9 2/7] media: platform: amd: low level support for isp4 firmware Bin Du
2026-03-02 7:30 ` [PATCH v9 3/7] media: platform: amd: Add isp4 fw and hw interface Bin Du
2026-03-02 7:30 ` [PATCH v9 4/7] media: platform: amd: isp4 subdev and firmware loading handling added Bin Du
2026-03-02 7:30 ` [PATCH v9 5/7] media: platform: amd: isp4 video node and buffers " Bin Du
2026-03-02 7:30 ` [PATCH v9 6/7] media: platform: amd: isp4 debug fs logging and more descriptive errors Bin Du
2026-03-02 7:30 ` [PATCH v9 7/7] Documentation: add documentation of AMD isp 4 driver Bin Du
2026-03-03 22:44 ` [PATCH] media: amd: isp4: add system suspend/resume support Kinn Coelho Juliao
2026-03-03 22:49 ` Mario Limonciello
2026-03-03 23:23 ` Nirujogi, Pratap
2026-03-04 0:28 ` Kinn Coelho Juliao [this message]
[not found] ` <bb32d3a9-51c1-4c56-9452-753c993c5316@amd.com>
2026-03-06 2:20 ` Kinn Julião
2026-03-06 3:58 ` Nirujogi, Pratap
[not found] ` <CAF+u_Bza2FStVhZEVzuVJjexteRkcK7OCAgTmEmyKDhrMCbBPg@mail.gmail.com>
2026-03-13 20:55 ` Mario Limonciello
2026-03-11 22:18 ` [PATCH v9 0/7] Add AMD ISP4 driver Sakari Ailus
2026-03-13 6:27 ` Du, Bin
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=20260304002811.95497-1-kinncj@gmail.com \
--to=kinncj@gmail.com \
--cc=Bin.Du@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=pratap.nirujogi@amd.com \
--cc=sultan@kerneltoast.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