From: "Yong Wu (吴勇)" <Yong.Wu@mediatek.com>
To: "Zhengnan Chen (陈征南)" <Zhengnan.Chen@mediatek.com>,
"robin.murphy@arm.com" <robin.murphy@arm.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"will@kernel.org" <will@kernel.org>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"iommu@lists.linux.dev" <iommu@lists.linux.dev>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/3] iommu/mediatek: Add support for mt8189
Date: Sun, 10 Aug 2025 07:09:53 +0000 [thread overview]
Message-ID: <7a2105e50f9543c4bd97c9d51aa09baaa3b72ed2.camel@mediatek.com> (raw)
In-Reply-To: <20250807095756.11840-4-zhengnan.chen@mediatek.com>
On Thu, 2025-08-07 at 17:57 +0800, zhengnan chen wrote:
> From: "zhengnan chen" <zhengnan.chen@mediatek.com>
>
> Add support for mt8189 INFRA & APU & MM IOMMUs.
>
> Signed-off-by: zhengnan chen <zhengnan.chen@mediatek.com>
Splitting this into three patches(apu/mm/infra) may make the patch more
readable.
> ---
> drivers/iommu/mtk_iommu.c | 76
> +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 76 insertions(+)
>
[snip]
> +
> +static const struct mtk_iommu_plat_data mt8189_data_mm = {
> + .m4u_plat = M4U_MT8189,
> + .flags = HAS_BCLK | HAS_SUB_COMM_3BITS |
> OUT_ORDER_WR_EN |
> + WR_THROT_EN | IOVA_34_EN | MTK_IOMMU_TYPE_MM
> |
> + PGTABLE_PA_35_EN | DL_WITH_MULTI_LARB,
> + .hw_list = &m4ulist,
> + .inv_sel_reg = REG_MMU_INV_SEL_GEN2,
> + .banks_num = 5,
> + .banks_enable = {true, false, false, false, true},
> + .iova_region = mt8192_multi_dom,
> + .iova_region_nr = ARRAY_SIZE(mt8192_multi_dom),
> + .iova_region_larb_msk = mt8189_larb_region_msk,
> + .larbid_remap = {{0}, {1}, {21/*GCE_D*/, 21/*GCE_M*/, 2},
Take care the format, Add space after '/*'
> + {19, 20, 9, 11}, {7}, {4},
> + {13, 17}, {14, 16}},
> +};
> +
> static const struct mtk_iommu_plat_data mt8192_data = {
> .m4u_plat = M4U_MT8192,
> .flags = HAS_BCLK | HAS_SUB_COMM_2BITS |
> OUT_ORDER_WR_EN |
> @@ -1826,6 +1899,9 @@ static const struct of_device_id
> mtk_iommu_of_ids[] = {
> { .compatible = "mediatek,mt8188-iommu-infra", .data =
> &mt8188_data_infra},
> { .compatible = "mediatek,mt8188-iommu-vdo", .data =
> &mt8188_data_vdo},
> { .compatible = "mediatek,mt8188-iommu-vpp", .data =
> &mt8188_data_vpp},
> + { .compatible = "mediatek,mt8189-iommu-apu", .data =
> &mt8189_data_apu},
> + { .compatible = "mediatek,mt8189-iommu-infra", .data =
> &mt8189_data_infra},
> + { .compatible = "mediatek,mt8189-iommu-mm", .data =
> &mt8189_data_mm},
> { .compatible = "mediatek,mt8192-m4u", .data = &mt8192_data},
> { .compatible = "mediatek,mt8195-iommu-infra", .data =
> &mt8195_data_infra},
> { .compatible = "mediatek,mt8195-iommu-vdo", .data =
> &mt8195_data_vdo},
prev parent reply other threads:[~2025-08-10 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 9:57 [PATCH 0/3] MT8189 IOMMU SUPPORT zhengnan chen
2025-08-07 9:57 ` [PATCH 1/3] dt-bindings: mediatek: mt8189: Add bindings for MM & APU & INFRA IOMMU zhengnan chen
2025-08-07 15:23 ` Matthias Brugger
2025-08-07 16:12 ` Conor Dooley
2025-08-07 9:57 ` [PATCH 2/3] iommu/mediatek: Add a flag DL_WITH_MULTI_LARB zhengnan chen
2025-08-07 15:24 ` Matthias Brugger
2025-08-10 7:09 ` Yong Wu (吴勇)
2025-08-07 9:57 ` [PATCH 3/3] iommu/mediatek: Add support for mt8189 zhengnan chen
2025-08-10 7:09 ` Yong Wu (吴勇) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7a2105e50f9543c4bd97c9d51aa09baaa3b72ed2.camel@mediatek.com \
--to=yong.wu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Zhengnan.Chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).