From: Haowen Tu <tuhaowen@uniontech.com>
To: rafael@kernel.org
Cc: lenb@kernel.org, pavel@kernel.org, linux-pm@vger.kernel.org,
laurent.pinchart@ideasonboard.com, hansg@kernel.org,
mchehab@kernel.org, linux-media@vger.kernel.org,
linux-kernel@vger.kernel.org, Haowen Tu <tuhaowen@uniontech.com>
Subject: [PATCH 0/2] PM: hibernate: add helper to detect image-write phase
Date: Tue, 28 Apr 2026 16:05:11 +0800 [thread overview]
Message-ID: <20260428080513.1833515-1-tuhaowen@uniontech.com> (raw)
During S4 hibernation, after create_image() saves the memory snapshot,
the kernel resumes devices with PMSG_THAW solely to write the hibernation
image to storage before final powerdown. Drivers unrelated to storage I/O
have no reason to reinitialize during this transient phase.
Drivers using dev_pm_ops already have separate .thaw and .restore
callbacks and can handle this natively. However, usb_driver.resume
takes no pm_message_t argument, so a USB driver cannot distinguish
PMSG_THAW from PMSG_RESTORE without an out-of-band query.
This series adds pm_hibernation_storing_image(), a small helper that
returns true during the image-write window. As a first user, the UVC
driver uses it to skip resume in uvc_video_resume() until the real
PMSG_RESTORE wake-up.
Tested with hibernation image written to local storage and resumed from
disk on a system with a USB UVC camera attached.
Haowen Tu (2):
pm/hibernate: add pm_hibernation_storing_image() helper
media: uvcvideo: skip resume when writing hibernation image
drivers/media/usb/uvc/uvc_video.c | 10 ++++++++++
include/linux/suspend.h | 2 ++
kernel/power/hibernate.c | 19 +++++++++++++++++++
3 files changed, 31 insertions(+)
--
2.20.1
next reply other threads:[~2026-04-28 8:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 8:05 Haowen Tu [this message]
2026-04-28 8:05 ` [PATCH 1/2] PM: hibernate: add pm_hibernation_storing_image() helper Haowen Tu
2026-04-28 8:05 ` [PATCH 2/2] media: uvcvideo: skip resume when writing hibernation image Haowen Tu
2026-04-28 8:36 ` Oliver Neukum
2026-04-28 8:58 ` Haowen Tu
2026-04-28 9:13 ` Laurent Pinchart
2026-04-29 1:15 ` Haowen Tu
2026-04-29 1:16 ` Haowen Tu
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=20260428080513.1833515-1-tuhaowen@uniontech.com \
--to=tuhaowen@uniontech.com \
--cc=hansg@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pavel@kernel.org \
--cc=rafael@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