summaryrefslogtreecommitdiffstats
path: root/kernel/rcutree_trace.c
diff options
context:
space:
mode:
authorFelipe Balbi <balbi@ti.com>2012-11-14 15:22:45 +0100
committerWolfram Sang <w.sang@pengutronix.de>2012-11-14 17:44:37 +0100
commitd60ece5f010043422c5fbc3609714c4420c7c9bf (patch)
tree442098ec524242561a86a8525aaa7a83cffa4911 /kernel/rcutree_trace.c
parentRevert "ARM: OMAP: convert I2C driver to PM QoS for MPU latency constraints" (diff)
downloadlinux-d60ece5f010043422c5fbc3609714c4420c7c9bf.tar.xz
linux-d60ece5f010043422c5fbc3609714c4420c7c9bf.zip
i2c: omap: ensure writes to dev->buf_len are ordered
if we allow compiler reorder our writes, we could fall into a situation where dev->buf_len is reset for no apparent reason. This bug was found with a simple script which would transfer data to an i2c client from 1 to 1024 bytes (a simple for loop), when we got to transfer sizes bigger than the fifo size, dev->buf_len was reset to zero before we had an oportunity to handle XDR Interrupt. Because dev->buf_len was zero, we entered omap_i2c_transmit_data() to transfer zero bytes, which would mean we would just silently exit omap_i2c_transmit_data() without actually writing anything to DATA register. That would cause XDR IRQ to trigger forever and we would never transfer the remaining bytes. After adding the memory barrier, we also drop resetting dev->buf_len to zero in omap_i2c_xfer_msg() because both omap_i2c_transmit_data() and omap_i2c_receive_data() will act until dev->buf_len reaches zero, rendering the other write in omap_i2c_xfer_msg() redundant. This patch has been tested with pandaboard for a few iterations of the script mentioned above. Signed-off-by: Felipe Balbi <balbi@ti.com> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Diffstat (limited to 'kernel/rcutree_trace.c')
0 files changed, 0 insertions, 0 deletions