diff options
| author |   Robin Murphy <robin.murphy@arm.com> | 2019-11-11 18:55:18 +0000 |
|---|---|---|
| committer |   Joerg Roedel <jroedel@suse.de> | 2019-11-12 17:07:47 +0100 |
| commit | 5b47748ecf2e3b7e346d6ce136e1c57239f995b0 (patch) | |
| tree | bf2154407d2a42c61defaf8777742ca656907243 /include/linux/iommu.h | |
| parent | iommu: rockchip: Free domain on .domain_free (diff) | |
| download | wireguard-linux-5b47748ecf2e3b7e346d6ce136e1c57239f995b0.tar.xz wireguard-linux-5b47748ecf2e3b7e346d6ce136e1c57239f995b0.zip | |
iommu/rockchip: Don't provoke WARN for harmless IRQs
Although we don't generally expect IRQs to fire for a suspended IOMMU,
there are certain situations (particularly with debug options) where
we might legitimately end up with the pm_runtime_get_if_in_use() call
from rk_iommu_irq() returning 0. Since this doesn't represent an actual
error, follow the other parts of the driver and save the WARN_ON()
condition for a genuine negative value. Even if we do have spurious
IRQs due to a wedged VOP asserting the shared line, it's not this
driver's job to try to second-guess the IRQ core to warn about that.
Reported-by: Vasily Khoruzhick <anarsoul@gmail.com>
Signed-off-by: Robin Murphy <robin.murphy@arm.com>
Acked-by: Marc Zyngier <maz@kernel.org>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'include/linux/iommu.h')
0 files changed, 0 insertions, 0 deletions