[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6b368ae8-7c9b-70b6-9858-025743c2bf7f@xs4all.nl>
Date: Tue, 21 Mar 2023 09:54:44 +0100
From: Hans Verkuil <hverkuil@...all.nl>
To: Yong Wu <yong.wu@...iatek.com>, Joerg Roedel <joro@...tes.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Rob Herring <robh+dt@...nel.org>
Cc: Will Deacon <will@...nel.org>, Robin Murphy <robin.murphy@....com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
nfraprado@...labora.com, linux-media@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
iommu@...ts.linux.dev,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>,
mingyuan.ma@...iatek.com, yf.wang@...iatek.com,
jianjiao.zeng@...iatek.com, Yunfei Dong <yunfei.dong@...iatek.com>,
kyrie wu <kyrie.wu@...iatek.corp-partner.google.com>,
chengci.xu@...iatek.com, youlin.pei@...iatek.com,
anan.sun@...iatek.com
Subject: Re: [PATCH v5 00/11] Adjust the dma-ranges for MTK IOMMU
On 07/03/2023 03:34, Yong Wu wrote:
> After commit f1ad5338a4d5 ("of: Fix "dma-ranges" handling for bus
> controllers"), the dma-ranges is not allowed for dts leaf node.
> but we still would like to separate the different masters into
> different iova regions. Thus we adjust the internal flow, separate
> the 16GB iova range by the master HW larbid/portid and add the
> dma-ranges property in the parent "soc" node. This also could avoid
> the users forget/abuse the iova regions.
>
> The commit f1ad5338a4d5 did affect the mt8195 venc, But it is not
> a fatal issue, it could also work well at 0-4GB iova. thus I don't
> add "Fixes:" tag.
>
> In this series, I add functions for mt8192/mt8195/mt8186, mt8188 will
> be in its special patchset. and the previous mt8173/mt8183...support
> 0-4GB only, no need this function.
>
> Change note:
> v5: Nothing change. Just rebase on v6.3-rc1.
>
> v4: https://lore.kernel.org/linux-mediatek/20230215062544.8677-1-yong.wu@mediatek.com/
> Improve the comment in the code from AngeloGioacchino.
>
> v3: https://lore.kernel.org/linux-mediatek/20230214031114.926-1-yong.wu@mediatek.com/
> Add a new patch only for comment more in the code.
>
> v2: https://lore.kernel.org/linux-mediatek/20230208053643.28249-1-yong.wu@mediatek.com/
> a) Base on next-20230206 since mt8195 jpeg node is applied which affect
> this patch.
> b) Reword the commit message [1/10][2/10] to explain effect.
>
> v1: https://lore.kernel.org/linux-mediatek/20230113060133.9394-1-yong.wu@mediatek.com/
> Base on v6.2-rc3.
>
> Yong Wu (11):
> dt-bindings: media: mediatek,vcodec: Remove dma-ranges property
> dt-bindings: media: mediatek,jpeg: Remove dma-ranges property
I assume that these two media bindings patches be pulled in through the iommu subsystem?
Or are they independent and can I take them?
Either is fine with me, I just need to know.
Regards,
Hans
> iommu/mediatek: Improve comment for the current region/bank
> iommu/mediatek: Get regionid from larb/port id
> iommu/mediatek: mt8192: Add iova_region_larb_msk
> iommu/mediatek: mt8195: Add iova_region_larb_msk
> iommu/mediatek: mt8186: Add iova_region_larb_msk
> iommu/mediatek: Add a gap for the iova regions
> arm64: dts: mt8195: Add dma-ranges for the parent "soc" node
> arm64: dts: mt8195: Remove the unnecessary dma-ranges
> arm64: dts: mt8186: Add dma-ranges for the parent "soc" node
>
> .../media/mediatek,mt8195-jpegdec.yaml | 7 -
> .../media/mediatek,mt8195-jpegenc.yaml | 7 -
> .../media/mediatek,vcodec-decoder.yaml | 5 -
> .../media/mediatek,vcodec-encoder.yaml | 5 -
> .../media/mediatek,vcodec-subdev-decoder.yaml | 7 -
> .../bindings/media/mediatek-jpeg-encoder.yaml | 5 -
> arch/arm64/boot/dts/mediatek/mt8186.dtsi | 1 +
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 4 +-
> drivers/iommu/mtk_iommu.c | 143 ++++++++++++++----
> 9 files changed, 114 insertions(+), 70 deletions(-)
>
Powered by blists - more mailing lists