summaryrefslogtreecommitdiffstats
path: root/drivers/iommu/omap-iommu.c
diff options
context:
space:
mode:
authorAnna-Maria Gleixner <anna-maria@linutronix.de>2018-07-20 10:45:45 +0200
committerJoerg Roedel <jroedel@suse.de>2018-07-20 14:36:19 +0200
commitf1a066fcc9725960a73c00267afe7e346cc9fc6f (patch)
treea8ba305f274d84549de250e374cee3b3c9df5c4d /drivers/iommu/omap-iommu.c
parent90fcffd9cf5e7cc593169f529799f3e3c5437e75 (diff)
downloadtalos-op-linux-f1a066fcc9725960a73c00267afe7e346cc9fc6f.tar.gz
talos-op-linux-f1a066fcc9725960a73c00267afe7e346cc9fc6f.zip
iommu/amd: Remove redundant WARN_ON()
The WARN_ON() was introduced in commit 272e4f99e966 ("iommu/amd: WARN when __[attach|detach]_device are called with irqs enabled") to ensure that the domain->lock is taken in proper irqs disabled context. This is required, because the domain->lock is taken as well in irq context. The proper context check by the WARN_ON() is redundant, because it is already covered by LOCKDEP. When working with locks and changing context, a run with LOCKDEP is required anyway and would detect the wrong lock context. Furthermore all callers for those functions are within the same file and all callers acquire another lock which already disables interrupts. Signed-off-by: Anna-Maria Gleixner <anna-maria@linutronix.de> Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/iommu/omap-iommu.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud