summaryrefslogtreecommitdiff
path: root/scripts/stackusage
diff options
context:
space:
mode:
authorBartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>2026-03-06 18:22:54 +0100
committerPhilipp Zabel <p.zabel@pengutronix.de>2026-03-09 10:20:04 +0100
commit8c91302a29bc1b710c7a164d4b81b5bb432f4eb5 (patch)
treece0e4efb88e043c4d1e650ecb85a5363b6302092 /scripts/stackusage
parent44a0acb2caca3bfd0ca459fbf0b19be75f1819c0 (diff)
reset: protect struct reset_control with its own mutex
Currently we use a single, global mutex - misleadingly names reset_list_mutex - to protect the global list of reset devices, per-controller list of reset control handles and also internal fields of struct reset_control. Locking can be made a lot more fine-grained if we use a separate mutex for serializing operations on the list AND accessing the reset control handle. Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com> Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions