mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-21 11:44:01 +08:00
a1a8e1dc11
When using more than one trigger consumer it can happen that multiple threads perform a read-modify-update cycle on 'use_count' concurrently. This can cause updates to be lost and use_count can get stuck at non-zero value, in which case the IIO core assumes that at least one thread is still running and will wait for it to finish before running any trigger handlers again. This effectively renders the trigger disabled and a reboot is necessary before it can be used again. To fix this make use_count an atomic variable. Also set it to the number of consumers before starting the first consumer, otherwise it might happen that use_count drops to 0 even though not all consumers have been run yet. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Tested-by: Denis Ciocca <denis.ciocca@st.com> Signed-off-by: Jonathan Cameron <jic23@kernel.org> |
||
|---|---|---|
| .. | ||
| adc | ||
| common | ||
| dac | ||
| frequency | ||
| gyro | ||
| imu | ||
| buffer.h | ||
| consumer.h | ||
| driver.h | ||
| events.h | ||
| iio.h | ||
| kfifo_buf.h | ||
| machine.h | ||
| sysfs.h | ||
| trigger_consumer.h | ||
| trigger.h | ||
| triggered_buffer.h | ||
| types.h | ||