summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2026-07-19 22:25:13 +0100
committerMark Brown <broonie@kernel.org>2026-07-19 22:25:13 +0100
commita9058504f11150308c44f6c0683eb04c822b821d (patch)
tree8bbeb9b212774f74d797462c17a70206a010fa84 /tools/perf/scripts/python/stackcollapse.py
parent8e29ed571788f41d1121e1e515ba8745695a38dc (diff)
parenta54bc0eef90ea760039c14bb7f3b5db42529f84d (diff)
ASoC: fsl: fix m2m_init error path cleanup in fsl_asrc and fsl_easrc
Shengjiu Wang <shengjiu.wang@nxp.com> says: Both fsl_asrc_probe() and fsl_easrc_probe() call fsl_asrc_m2m_init() near the end of their probe functions. On failure, the original code did a bare return ret, bypassing the existing error labels that call pm_runtime_disable(). This leaves runtime PM enabled and the device in an inconsistent state after a failed probe. Fix both drivers by replacing the bare return with a goto to the appropriate cleanup label (err_pm_get_sync for fsl_asrc and err_pm_disable for fsl_easrc), ensuring pm_runtime_disable() is always called on the probe error path. Link: https://patch.msgid.link/20260715024758.1252801-1-shengjiu.wang@oss.nxp.com
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions