[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <02719a0f-9725-abc5-f5c4-acbb4bfac08d@collabora.com>
Date: Mon, 10 Jan 2022 12:44:32 +0100
From: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
To: Dafna Hirschfeld <dafna.hirschfeld@...labora.com>,
iommu@...ts.linux-foundation.org, Yong Wu <yong.wu@...iatek.com>,
Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
"moderated list:MEDIATEK IOMMU DRIVER"
<linux-mediatek@...ts.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-arm-kernel@...ts.infradead.org>,
open list <linux-kernel@...r.kernel.org>, kernel@...labora.com,
linux-media@...r.kernel.org, sebastian.reichel@...labora.com
Subject: Re: [PATCH v2 5/5] iommu/mediatek: Always tlb_flush_all when each PM
resume
Il 08/12/21 13:07, Dafna Hirschfeld ha scritto:
> From: Yong Wu <yong.wu@...iatek.com>
>
> 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 <yong.wu@...iatek.com>
> [move the call to mtk_iommu_tlb_flush_all to the bottom of resume cb, improve doc/log]
> Signed-off-by: Dafna Hirschfeld <dafna.hirschfeld@...labora.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Powered by blists - more mailing lists