From 4c91a2f4805c3b44849526330c4600d4bd2de176 Mon Sep 17 00:00:00 2001 From: Brian Norris Date: Tue, 29 Sep 2026 19:49:49 -0700 Subject: [PATCH] PM: runtime: Correct pm_runtime_autosuspend_expiration() doc The "adjusted to be nonzero" comment may be a relic from when this API previously used jiffies, although I'm not quite sure about that either. In any case, it doesn't seem correct today. Signed-off-by: Brian Norris Link: https://patch.msgid.link/20260929194956.v3.1.Ifc8b2d1742729cc82f46220d85c6382fdee1fc8b@changeid Signed-off-by: Rafael J. Wysocki --- drivers/base/power/runtime.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/base/power/runtime.c b/drivers/base/power/runtime.c index 655c0b8af095..bb366a295a73 100644 --- a/drivers/base/power/runtime.c +++ b/drivers/base/power/runtime.c @@ -169,7 +169,7 @@ static void pm_runtime_cancel_pending(struct device *dev) * Compute the autosuspend-delay expiration time based on the device's * power.last_busy time. If the delay has already expired or is disabled * (negative) or the power.use_autosuspend flag isn't set, return 0. - * Otherwise return the expiration time in nanoseconds (adjusted to be nonzero). + * Otherwise return the expiration time in nanoseconds. * * This function may be called either with or without dev->power.lock held. * Either way it can be racy, since power.last_busy may be updated at any time.