[PATCH] i2c: omap: ensure writes to dev->buf_len are ordered
From: Felipe Balbi <hidden>
Date: 2012-10-25 18:03:40
Also in:
linux-i2c, linux-omap
Possibly related (same subject, not in this thread)
- 2012-11-02 · [PATCH] i2c: omap: ensure writes to dev->buf_len are ordered · Felipe Balbi <hidden>
- 2012-11-01 · [PATCH] i2c: omap: ensure writes to dev->buf_len are ordered · Wolfram Sang <hidden>
- 2012-10-28 · [PATCH] i2c: omap: ensure writes to dev->buf_len are ordered · Santosh Shilimkar <hidden>
- 2012-10-27 · [PATCH] i2c: omap: ensure writes to dev->buf_len are ordered · paul@pwsan.com (Paul Walmsley)
- 2012-10-27 · [PATCH] i2c: omap: ensure writes to dev->buf_len are ordered · Santosh Shilimkar <hidden>
Hi, On Thu, Oct 25, 2012 at 09:38:06AM -0700, Kevin Hilman wrote:
+Paul Felipe Balbi [off-list ref] writes:quoted
if we allow compiler reorder our writes, we could fall into a situation where dev->buf_len is reset for no apparent reason.Any chance this would help with the bug Paul found with I2C timeouts on beagle userspace startup?
I replied to the original thread asking the same ;-) -- balbi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20121025/8550556d/attachment-0001.sig>