i2c: tegra: Better handle case where CPU0 is busy for a long time

Browse source

Boot CPU0 always handle I2C interrupt and under some rare circumstances
(like running KASAN + NFS root) it may stuck in uninterruptible state for
a significant time. In this case we will get timeout if I2C transfer is
running on a sibling CPU, despite of IRQ being raised. In order to handle
this rare condition, the IRQ status needs to be checked after completion
timeout.

Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>

...

This commit is contained in:

Dmitry Osipenko 2020-03-24 22:12:16 +03:00 • committed by Thierry Reding

parent 26ca88aaea

commit 566c05f7cd

1 changed files with 15 additions and 12 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

27

drivers/i2c/busses/i2c-tegra.c

View file