Home
last modified time | relevance | path

Searched full:m4u (Results 1 – 14 of 14) sorted by relevance

/Linux-v5.15/Documentation/devicetree/bindings/iommu/
Dmediatek,iommu.yaml13 Some MediaTek SOCs contain a Multimedia Memory Management Unit (M4U), and
14 this M4U have two generations of HW architecture. Generation one uses flat
18 About the M4U Hardware Block Diagram, please check below:
22 m4u (Multimedia Memory Management Unit)
52 As above, The Multimedia HW will go through SMI and M4U while it
53 access EMI. SMI is a bridge between m4u and the Multimedia HW. It contain
55 HW should go though the m4u for translation or bypass it and talk
65 smi-common and m4u, and additional GALS module between smi-larb and
73 - mediatek,mt2701-m4u # generation one
74 - mediatek,mt2712-m4u # generation two
[all …]
/Linux-v5.15/include/dt-bindings/memory/
Dmt2701-larb-port.h11 * Mediatek m4u generation 1 such as mt2701 has flat m4u port numbers,
15 * But m4u generation 2 like mt8173 have different port number, it use fixed
/Linux-v5.15/drivers/iommu/
Dmtk_iommu.c143 * In M4U 4GB mode, the physical address is remapped as below:
159 * The Region 'A'(I/O) can NOT be mapped by M4U; For Region 'B'/'C'/'D', the
166 static LIST_HEAD(m4ulist); /* List all the M4U HWs */
190 * There may be 1 or 2 M4U HWs, But we always expect they are in the same domain
193 * Here always return the mtk_iommu_data of the first probed M4U where the
469 if (!data->m4u_dom) { /* Initialize the M4U HW */ in mtk_iommu_attach_device()
503 /* The "4GB mode" M4U physically can not use the lower remap of Dram. */ in mtk_iommu_map()
617 /* Get the m4u device */ in mtk_iommu_of_xlate()
1048 { .compatible = "mediatek,mt2712-m4u", .data = &mt2712_data},
1049 { .compatible = "mediatek,mt6779-m4u", .data = &mt6779_data},
[all …]
DKconfig423 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
430 tristate "MediaTek IOMMU Version 1 (M4U gen1) Support"
438 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
Dmtk_iommu_v1.c3 * IOMMU API for MTK architected m4u v1 implementations
85 * MTK m4u support 4GB iova address space, and only support 4K page
389 /* Get the m4u device */ in mtk_iommu_create_mapping()
533 { .compatible = "mediatek,mt2701-m4u", },
702 MODULE_DESCRIPTION("IOMMU API for MediaTek M4U v1 implementations");
/Linux-v5.15/arch/arm64/boot/dts/mediatek/
Dmt8167.dtsi174 iommu: m4u@10203000 {
175 compatible = "mediatek,mt8167-m4u";
Dmt2712e.dtsi327 compatible = "mediatek,mt2712-m4u";
344 compatible = "mediatek,mt2712-m4u";
Dmt8183.dtsi618 compatible = "mediatek,mt8183-m4u";
Dmt8173.dtsi586 compatible = "mediatek,mt8173-m4u";
/Linux-v5.15/arch/arm/boot/dts/
Dmt7623n.dtsi104 compatible = "mediatek,mt7623-m4u",
105 "mediatek,mt2701-m4u";
Dmt2701.dtsi220 compatible = "mediatek,mt2701-m4u";
/Linux-v5.15/Documentation/devicetree/bindings/memory-controllers/
Dmediatek,smi-larb.yaml62 hardward id is not consecutive from its M4U point of view.
/Linux-v5.15/drivers/memory/
Dmtk-smi.c217 /* do not need to enable m4u for this port */ in mtk_smi_larb_config_port_gen1()
524 * m4u port, and we need to enable the aync clock for transform the smi in mtk_smi_common_probe()
/Linux-v5.15/sound/usb/
Dmidi.c1384 case USB_ID(0x0a92, 0x1020): /* ESI M4U */ in snd_usbmidi_out_endpoint_create()