diff options
| author | Ridham Khurana <khurana.ridham222@gmail.com> | 2026-09-22 09:20:58 +0000 |
|---|---|---|
| committer | Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com> | 2026-09-23 10:13:46 +0200 |
| commit | e9438ab5328a177c9c0e5df87eb92a7162841e98 (patch) | |
| tree | 270e1c5f409b61f3934a1fb93bd9a2f9045861d4 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 1feb5d39b05afd902ed9fc902ec5b15be03a4bdb (diff) | |
| download | linux-next-e9438ab5328a177c9c0e5df87eb92a7162841e98.tar.gz linux-next-e9438ab5328a177c9c0e5df87eb92a7162841e98.zip | |
gpio: zynq: fix runtime PM leak on request error path
pm_runtime_get_sync() leaves the usage counter incremented even when it
fails, and zynq_gpio_request() returns the error without dropping it.
gpiolib does not call ->free() when ->request() fails, so zynq_gpio_free(),
which holds the only matching pm_runtime_put(), never runs. The reference
is leaked and the controller can no longer runtime-suspend, so its clock
stays enabled.
Switch to pm_runtime_resume_and_get(), which only increments the usage
counter on success.
Fixes: 3242ba117e9b ("gpio: Add driver for Zynq GPIO controller")
Cc: stable@vger.kernel.org
Signed-off-by: Ridham Khurana <khurana.ridham222@gmail.com>
Link: https://patch.msgid.link/20260922092102.1053513-1-khurana.ridham222@gmail.com
Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions