From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com
Cc: linux-usb@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/1] PM: runtime: change stub pm_runtime_get_if_active() return 1 when !CONFIG_PM
Date: Thu, 29 Oct 2026 16:43:35 +0000 [thread overview]
Message-ID: <sashiko-outbox-189670@kernel.org> (raw)
In-Reply-To: <20261029163044.3062958-1-Frank.Li@oss.nxp.com>
> From: Frank Li <Frank.Li@nxp.com>
>
> When CONFIG_PM is not enabled, all devices runtime PM state should be
> treated as active.
>
> __pm_runtime_resume() returns 1 (called by pm_runtime_get()).
> pm_runtime_get_if_active() is the try-and-get version of pm_runtime_get().
> stub pm_runtime_active() also returns true. So pm_runtime_get_if_active()
> should return the same value as the stub pm_runtime_get(), which is 1.
>
> Analysis of all callers and their behavior with old (-EINVAL) vs new (1):
>
> Pattern A: if (!pm_runtime_get_if_active(dev)) -- no impact
> Both -EINVAL and 1 are non-zero, so !ret is false in both cases.
> Callers: drivers/accel/ethosu/ethosu_perfmon.c,
> [ ... ]
> Both succeed when CONFIG_PM is disabled; functionally equivalent.
> drivers/hwmon/eic7700-pvt.c: call is guarded by IS_ENABLED(CONFIG_PM),
> stub is never reached. No impact.
>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261029163044.3062958-1-Frank.Li@oss.nxp.com?part=1
next prev parent reply other threads:[~2026-10-29 16:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 16:30 [PATCH 1/1] PM: runtime: change stub pm_runtime_get_if_active() return 1 when !CONFIG_PM Frank.Li
2026-10-29 16:32 ` ✗ LGCI.VerificationFailed: failure for series starting with [1/1] " Patchwork
2026-10-29 16:43 ` sashiko-bot [this message]
2026-10-29 18:11 ` [PATCH 1/1] " Alex Elder
2026-10-29 18:59 ` Dan Carpenter
2026-10-30 8:57 ` Sakari Ailus
2026-10-30 13:46 ` Alex Elder
2026-10-30 13:54 ` Dan Carpenter
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=sashiko-outbox-189670@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@oss.nxp.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.