Revision 96219c3a257cc8ba3b3cae67efdc88be37cf7c9d authored by Doug Anderson on 30 August 2011, 17:46:10 UTC, committed by Ben Dooks on 06 September 2011, 23:13:40 UTC
In tegra_i2c_fill_tx_fifo, once we have finished pushing all the bytes to the I2C hardware controller, the interrupt might happen before we have updated i2c_dev->msg_buf_remaining at the end of the function. Then, in tegra_i2c_isr, we will call again tegra_i2c_fill_tx_fifo triggering weird behaviour. This has been shown to happen under real conditions. Signed-off-by: Doug Anderson <dianders@chromium.org> Tested-by: Vincent Palatin <vpalatin@chromium.org> Acked-by: Rhyland Klein <rklein@nvidia.com> Acked-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Ben Dooks <ben-linux@fluff.org>
1 parent 048e29c
File | Mode | Size |
---|---|---|
hidraw | ||
hw_breakpoint | ||
kdb | ||
kfifo | ||
kobject | ||
kprobes | ||
trace_events | ||
tracepoints | ||
Kconfig | -rw-r--r-- | 1.8 KB |
Makefile | -rw-r--r-- | 148 bytes |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...