summaryrefslogtreecommitdiff
path: root/include/linux/coresight.h
diff options
context:
space:
mode:
authorJames Clark <james.clark@linaro.org>2024-11-28 12:14:14 +0000
committerSuzuki K Poulose <suzuki.poulose@arm.com>2024-12-11 10:15:25 +0000
commit5aec7c065fba0c56d6c1ea5d629395210f174be8 (patch)
treefbd8ff0eb9e4876ec495b591aebc9f9589db2312 /include/linux/coresight.h
parentc8ea5f41b4212fd6c76070bd9432f1bdec64f6b0 (diff)
coresight: Drop atomics in connection refcounts
These belong to the device being enabled or disabled and are only ever used inside the device's spinlock. Remove the atomics to not imply that there are any other concurrent accesses. If atomics were necessary I don't think they would have been enough anyway. There would be nothing to prevent an enable or disable running concurrently if not for the spinlock. Signed-off-by: James Clark <james.clark@linaro.org> Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com> Signed-off-by: Suzuki K Poulose <suzuki.poulose@arm.com> Link: https://lore.kernel.org/r/20241128121414.2425119-1-james.clark@linaro.org
Diffstat (limited to 'include/linux/coresight.h')
-rw-r--r--include/linux/coresight.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/include/linux/coresight.h b/include/linux/coresight.h
index c13342594278..834029cb9ba2 100644
--- a/include/linux/coresight.h
+++ b/include/linux/coresight.h
@@ -200,8 +200,8 @@ struct coresight_connection {
struct coresight_device *dest_dev;
struct coresight_sysfs_link *link;
struct coresight_device *src_dev;
- atomic_t src_refcnt;
- atomic_t dest_refcnt;
+ int src_refcnt;
+ int dest_refcnt;
};
/**