summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorBrian Norris <briannorris@chromium.org>2026-10-06 16:13:33 -0700
committerBartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>2026-10-10 10:42:08 +0200
commit9bcd1725b0cc7954525e3d0d02fecaec7c7aab33 (patch)
tree2e2ed5a32ded5517321d5072a4b16824d2570534 /tools/perf/scripts/python
parent4d7c9430a26aea6a69521af3aa2d78dd5bc8d3ed (diff)
downloadlinux-next-9bcd1725b0cc7954525e3d0d02fecaec7c7aab33.tar.gz
linux-next-9bcd1725b0cc7954525e3d0d02fecaec7c7aab33.zip
pinctrl: qcom: lpass-lpi: Discard pm_runtime_put_autosuspend() return values
Passing the pm_runtime_put_autosuspend() return value to callers is not particularly useful. Returning an error code from pm_runtime_put_autosuspend() merely means that it has not queued up a timer or work item to check whether or not the device can be suspended and there are many perfectly valid situations in which that can happen, like after writing "on" to the device's runtime PM "control" attribute in sysfs for one example. Accordingly, update the LPASS LPI pinctrl driver to simply discard the return value of pm_runtime_put_autosuspend() and return 0 to the callers. This will facilitate a planned change of the pm_runtime_put_autosuspend() return type to void in the future, similar to commit 3afd8df02433 ("PM: runtime: Change pm_runtime_put() return type to void"). Signed-off-by: Brian Norris <briannorris@chromium.org> Acked-by: Linus Walleij <linusw@kernel.org> Link: https://patch.msgid.link/20261006161337.5.Ica4bfaf179a86c8d77f8f845826602914b81181b@changeid Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions