summaryrefslogtreecommitdiff
path: root/drivers/memory
diff options
context:
space:
mode:
authorYong Wu <yong.wu@mediatek.com>2019-11-04 15:01:03 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-01-17 19:48:59 +0100
commitf07d3e39f082e7d07d3f085641c35f3b5e553753 (patch)
tree16021a13e2ba9730d02967e58aa4346a3cac0d6a /drivers/memory
parente5c3362bc211bd0c38bd7accac690fdd098978a8 (diff)
downloadlinux-f07d3e39f082e7d07d3f085641c35f3b5e553753.tar.gz
linux-f07d3e39f082e7d07d3f085641c35f3b5e553753.tar.bz2
linux-f07d3e39f082e7d07d3f085641c35f3b5e553753.zip
iommu/mediatek: Add a new tlb_lock for tlb_flush
commit da3cc91b8db403728cde03c8a95cba268d8cbf1b upstream. The commit 4d689b619445 ("iommu/io-pgtable-arm-v7s: Convert to IOMMU API TLB sync") help move the tlb_sync of unmap from v7s into the iommu framework. It helps add a new function "mtk_iommu_iotlb_sync", But it lacked the lock, then it will cause the variable "tlb_flush_active" may be changed unexpectedly, we could see this warning log randomly: mtk-iommu 10205000.iommu: Partial TLB flush timed out, falling back to full flush The HW requires tlb_flush/tlb_sync in pairs strictly, this patch adds a new tlb_lock for tlb operations to fix this issue. Fixes: 4d689b619445 ("iommu/io-pgtable-arm-v7s: Convert to IOMMU API TLB sync") Signed-off-by: Yong Wu <yong.wu@mediatek.com> Signed-off-by: Joerg Roedel <jroedel@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/memory')
0 files changed, 0 insertions, 0 deletions