summaryrefslogtreecommitdiff
path: root/tools/lib/python
diff options
context:
space:
mode:
authorLeo Yan <leo.yan@arm.com>2026-02-24 10:56:14 +0000
committerSuzuki K Poulose <suzuki.poulose@arm.com>2026-02-25 09:25:28 +0000
commit55bf8be6f4a80d44c7f10e9d39b583e9645edf93 (patch)
treecd12f0272797683793e7593019aed3cd38ddb396 /tools/lib/python
parent6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f (diff)
coresight: cti: Move resource release to cti_remove()
Currently, CTI driver releases resource by deferring cti_device_release() to the device unregistration: cti_remove() `> coresight_unregister() `> cti_remove_assoc_from_csdev() `> device_unregister() `> cti_device_release() `> mutex_lock(&ect_mutex) `> release CTI resource `> mutex_unlock(&ect_mutex) In the above flow, two different CTI release callbacks are involved: cti_remove_assoc_from_csdev() and cti_device_release(). The former is used by a CoreSight device to unbind its associated CTI helper device, while the latter releases resources for the CTI device itself. Since there is no dependency between them, it is unnecessary to defer the CTI resource release until device unregistration. This commit releases the resources directly in cti_remove() and remove the injected release callback. Signed-off-by: Leo Yan <leo.yan@arm.com> Reviewed-by: Mike Leach <mike.leach@arm.com> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com> Link: https://lore.kernel.org/r/20260224-arm_coresight_refactor_cti_resource_release-v1-1-ff1b2bca9176@arm.com
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions