From: Bart Van Assche <bvanassche@acm.org>
To: Stanley Jhu <stanleyjhu@google.com>,
"Rafael J . Wysocki" <rafael@kernel.org>
Cc: Brian Norris <briannorris@chromium.org>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@kernel.org>,
Praveen Talari <praveen.talari@oss.qualcomm.com>,
Jonathan Corbet <corbet@lwn.net>, Mark Brown <broonie@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Jens Axboe <axboe@kernel.dk>,
linux-pm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] PM: runtime: Update runtime_pm.rst for non-fatal resume errors
Date: Wed, 4 Nov 2026 09:11:40 -0800 [thread overview]
Message-ID: <8adcbd80-f684-4e00-81b3-a2661fac895b@acm.org> (raw)
In-Reply-To: <20261104151651.3035537-1-stanleyjhu@google.com>
On 11/4/26 7:16 AM, Stanley Jhu wrote:
> + * If the resume callback returns an error code, the PM core sets the
> + device's runtime PM status back to 'suspended' and returns the error
> + code from synchronous resume helpers. Unlike with the suspend
> + callback, failures in the resume callback are never considered
fatal,
> + so the helper functions described in `Section 4`_ are not
blocked and
> + a subsequent resume request can run the resume callback again.
Hi Stanley,
This matches what rpm_resume() does since commit eef1d74bf88f. A nit:
suspend callback failures with -EBUSY / -EAGAIN are not fatal either,
so "Unlike most suspend callback errors" may be slightly more accurate.
Either way:
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Additionally, the kerneldoc of @runtime_error in include/linux/pm.h
("Fatal error code returned by a failing callback") could be updated
in a follow-up patch to mention ->runtime_suspend() explicitly.
Thanks,
Bart.
next prev parent reply other threads:[~2026-11-04 17:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 15:16 Stanley Jhu
2026-11-04 16:46 ` Brian Norris
2026-11-04 17:11 ` Bart Van Assche [this message]
2026-11-04 19:11 ` Rafael J. Wysocki (Intel)
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=8adcbd80-f684-4e00-81b3-a2661fac895b@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=briannorris@chromium.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=lenb@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=praveen.talari@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=stanleyjhu@google.com \
--cc=stern@rowland.harvard.edu \
/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®