diff options
author | Julian Wiedmann <jwi@linux.vnet.ibm.com> | 2018-03-21 17:14:00 +0100 |
---|---|---|
committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2018-04-10 07:38:58 +0200 |
commit | 89286320a236d245834075fa13adb0bdd827ecaa (patch) | |
tree | eac0fb567adcdc5da8d6e86d2afee4fa49e0b7c3 /drivers/platform | |
parent | ab7efda477f976c22f1d35797c33f22612d93182 (diff) | |
download | linux-89286320a236d245834075fa13adb0bdd827ecaa.tar.gz linux-89286320a236d245834075fa13adb0bdd827ecaa.tar.bz2 linux-89286320a236d245834075fa13adb0bdd827ecaa.zip |
s390/qdio: clear intparm during shutdown
During shutdown, qdio returns its ccw device back to control by the
upper-layer driver. But there is a remote chance that by the time where the
IRQ handler gets switched back, the interrupt for the preceding
ccw_device_{clear,halt} hasn't been presented yet.
Upper-layer drivers would then need to handle this IRQ - and since the IO
is issued with an intparm, it could very well be confused with whatever
intparm mechanism the driver uses itself (eg intparm == request address).
So when switching over the IRQ handler, also clear the intparm and have
upper-layer drivers deal with any such delayed interrupt as if it was
unsolicited.
Suggested-by: Sebastian Ott <sebott@linux.vnet.ibm.com>
Signed-off-by: Julian Wiedmann <jwi@linux.vnet.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'drivers/platform')
0 files changed, 0 insertions, 0 deletions