| commit | 02ab851324dc7e2fc75787f7fae71187092be7ed | |
| author | Benjamin Herrenschmidt <benh@kernel.crashing.org> | |
| Sun, 10 Jan 2010 17:51:42 +0000 (10 17:51 +0000) | ||
| committer | Benjamin Herrenschmidt <benh@kernel.crashing.org> | |
| Fri, 15 Jan 2010 02:26:13 +0000 (15 13:26 +1100) | ||
| tree | b7019a603013ccdeb176349a5b0e315111b2e538 | treesnapshot (tar.gz zip) |
| parent | 46759a7c132648d79121518d2f7c34edc3f0cf58 | commitdiff |
serial/pmac_zilog: Workaround problem due to interrupt on closed port
It seems that in qemu, we can see an interrupt in R3 despite the
fact that it's masked in W1. The chip doesn't actually issue an
interrupt, but we can "see" it when taking an interrupt for the
other channel. This may be a qemu bug ... or not, so let's be
safe and avoid calling into the UART layer when that happens which
woulc cause a crash.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Acked-by: Rob Landley <rob@landley.net>
It seems that in qemu, we can see an interrupt in R3 despite the
fact that it's masked in W1. The chip doesn't actually issue an
interrupt, but we can "see" it when taking an interrupt for the
other channel. This may be a qemu bug ... or not, so let's be
safe and avoid calling into the UART layer when that happens which
woulc cause a crash.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Acked-by: Rob Landley <rob@landley.net>
| drivers/serial/pmac_zilog.c | diffblobblamehistory |