diff options
author | Yong Wu <[email protected]> | 2021-12-08 14:07:44 +0200 |
---|---|---|
committer | Joerg Roedel <[email protected]> | 2022-03-04 11:04:45 +0100 |
commit | 4f23f6d45821701c68b99c2847a075472b53198c (patch) | |
tree | f4a0e91030867fa221349f879f75cad5d461d720 /tools/testing/selftests/bpf/progs/test_prog_array_init.c | |
parent | 15672b6dc5d03a947e9180db1d6564f43b0c6799 (diff) |
iommu/mediatek: Always tlb_flush_all when each PM resume
Prepare for 2 HWs that sharing pgtable in different power-domains.
When there are 2 M4U HWs, it may has problem in the flush_range in which
we get the pm_status via the m4u dev, BUT that function don't reflect the
real power-domain status of the HW since there may be other HW also use
that power-domain.
DAM allocation is often done while the allocating device is runtime
suspended. In such a case the iommu will also be suspended and partial
flushing of the tlb will not be executed.
Therefore, we add a tlb_flush_all in the pm_runtime_resume to make
sure the tlb is always clean.
In other case, the iommu's power should be active via device
link with smi.
Signed-off-by: Yong Wu <[email protected]>
[move the call to mtk_iommu_tlb_flush_all to the bottom of resume cb, improve doc/log]
Signed-off-by: Dafna Hirschfeld <[email protected]>
Reviewed-by: AngeloGioacchino Del Regno <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Joerg Roedel <[email protected]>
Diffstat (limited to 'tools/testing/selftests/bpf/progs/test_prog_array_init.c')
0 files changed, 0 insertions, 0 deletions