diff options
author | Russell King <rmk+kernel@arm.linux.org.uk> | 2015-06-06 23:41:09 +0300 |
---|---|---|
committer | Russell King <rmk+kernel@arm.linux.org.uk> | 2015-09-15 18:19:48 +0300 |
commit | f84a97d4804a09240372dc7b195f9d6162152228 (patch) | |
tree | 277ad69fe69e1a4137138b37d057e7a24e738348 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 3f3d0d00734de56a0c5996f4e4433046c745592e (diff) | |
download | linux-f84a97d4804a09240372dc7b195f9d6162152228.tar.xz |
drm/i2c: tda998x: report whether we actually handled the IRQ
Rather than always reporting that the interrupt was handled, we should
report whether we did handle the interrupt. Arrange to report IRQ_NONE
for cases where we found nothing to do.
This allows us to (eventually) recover from stuck-IRQ problems, rather
than causing the kernel to solidly lock up.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions