summaryrefslogtreecommitdiff
path: root/include/dt-bindings/gpio/meson-gxbb-gpio.h
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2017-02-03 12:39:46 +0100
committerMark Brown <broonie@kernel.org>2017-02-03 12:39:46 +0100
commit206c4720092d2a24bfefc041b377e889a220ffbf (patch)
tree2360fff83a9313d5c1d8c611cbcf7a55ecd5276d /include/dt-bindings/gpio/meson-gxbb-gpio.h
parentd0e287a401d9acf67b75180b26e2d62b7d482652 (diff)
parent1372cef1c697d8aac0cc923f8aa2c37d790ec9ed (diff)
parentb98acbff9a05b371c5f0ca6e44a3af8ce9274379 (diff)
Merge remote-tracking branches 'regulator/fix/fixed' and 'regulator/fix/twl6040' into regulator-linus
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-01-21 14:21:16 +0000
rk_list' is protected by `pch->lock'. I don't know if this may cause race conditions. Similarly `pch->cyclic' is written by `pl330_alloc_chan_resources' under `pl330->lock' but read by `pl330_tx_submit' under `pch->lock'. Second, I have removed locking from `pl330_request_channel' and `pl330_release_channel' functions. Function `pl330_request_channel' is only called from `pl330_alloc_chan_resources', so the lock is already held. Function `pl330_release_channel' is called from `pl330_free_chan_resources', which already holds the lock, and from `pl330_del'. Function `pl330_del' is called in an error path of `pl330_probe' and at the end of `pl330_remove', but I assume that there cannot be concurrent accesses to the protected data at those points. Signed-off-by: Iago Abal <mail@iagoabal.eu> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'tools/virtio/virtio-trace/Makefile')