Lars-Peter Clausen d7c773412f iio: ad_sigma_delta: Properly handle SPI bus locking vs CS assertion ... [ Upstream commit df1d80aee9 ] For devices from the SigmaDelta family we need to keep CS low when doing a conversion, since the device will use the MISO line as a interrupt to indicate that the conversion is complete. This is why the driver locks the SPI bus and when the SPI bus is locked keeps as long as a conversion is going on. The current implementation gets one small detail wrong though. CS is only de-asserted after the SPI bus is unlocked. This means it is possible for a different SPI device on the same bus to send a message which would be wrongfully be addressed to the SigmaDelta device as well. Make sure that the last SPI transfer that is done while holding the SPI bus lock de-asserts the CS signal. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Alexandru Ardelean <Alexandru.Ardelean@analog.com> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> Signed-off-by: Sasha Levin <sashal@kernel.org>		2019-05-31 06:46:24 -07:00
..
accel
adc	iio: ad_sigma_delta: Properly handle SPI bus locking vs CS assertion	2019-05-31 06:46:24 -07:00
common
dac
frequency
gyro
imu
magnetometer
timer
buffer-dma.h
buffer-dmaengine.h
buffer.h
buffer_impl.h
configfs.h
consumer.h
driver.h
events.h
hw-consumer.h
iio.h
kfifo_buf.h
machine.h
sw_device.h
sw_trigger.h
sysfs.h
trigger.h
trigger_consumer.h
triggered_buffer.h
triggered_event.h
types.h