[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f91157b6-886c-2d69-451e-6ddeb52f95d7@collabora.com>
Date: Mon, 10 Jan 2022 12:43:18 +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 2/5] iommu/mediatek: Always check runtime PM status in
tlb flush range callback
Il 08/12/21 13:07, Dafna Hirschfeld ha scritto:
> From: Sebastian Reichel <sebastian.reichel@...labora.com>
>
> In case of v4l2_reqbufs() it is possible, that a TLB flush is done
> without runtime PM being enabled. In that case the "Partial TLB flush
> timed out, falling back to full flush" warning is printed.
>
> Commit c0b57581b73b ("iommu/mediatek: Add power-domain operation")
> introduced has_pm as optimization to avoid checking runtime PM
> when there is no power domain attached. But without the PM domain
> there is still the device driver's runtime PM suspend handler, which
> disables the clock. Thus flushing should also be avoided when there
> is no PM domain involved.
>
> Signed-off-by: Sebastian Reichel <sebastian.reichel@...labora.com>
> Reviewed-by: Dafna Hirschfeld <dafna.hirschfeld@...labora.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>
Powered by blists - more mailing lists