Home
last modified time | relevance | path

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

/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/iommu/
H A 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 …]
/OK3568_Linux_fs/kernel/include/dt-bindings/memory/
H A 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
/OK3568_Linux_fs/kernel/drivers/iommu/
H A Dmtk_iommu.c144 * In M4U 4GB mode, the physical address is remapped as below:
160 * The Region 'A'(I/O) can NOT be mapped by M4U; For Region 'B'/'C'/'D', the
167 static LIST_HEAD(m4ulist); /* List all the M4U HWs */
191 * There may be 1 or 2 M4U HWs, But we always expect they are in the same domain
194 * Here always return the mtk_iommu_data of the first probed M4U where the
480 if (!data->m4u_dom) { /* Initialize the M4U HW */ in mtk_iommu_attach_device()
519 /* The "4GB mode" M4U physically can not use the lower remap of Dram. */ in mtk_iommu_map()
639 /* Get the m4u device */ in mtk_iommu_of_xlate()
1071 { .compatible = "mediatek,mt2712-m4u", .data = &mt2712_data},
1072 { .compatible = "mediatek,mt6779-m4u", .data = &mt6779_data},
[all …]
H A DKconfig385 Support for the M4U on certain Mediatek SOCs. M4U is MultiMedia
392 bool "MTK IOMMU Version 1 (M4U gen1) Support"
400 Support for the M4U on certain Mediatek SoCs. M4U generation 1 HW is
H A Dmtk_iommu_v1.c3 * IOMMU API for MTK architected m4u v1 implementations
86 * MTK m4u support 4GB iova address space, and only support 4K page
390 /* Get the m4u device */ in mtk_iommu_create_mapping()
535 { .compatible = "mediatek,mt2701-m4u", },
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A Dmt7623n.dtsi104 compatible = "mediatek,mt7623-m4u",
105 "mediatek,mt2701-m4u";
H A Dmt2701.dtsi220 compatible = "mediatek,mt2701-m4u";
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/memory-controllers/
H A Dmediatek,smi-larb.yaml62 hardward id is not consecutive from its M4U point of view.
/OK3568_Linux_fs/kernel/drivers/memory/
H A Dmtk-smi.c217 /* do not need to enable m4u for this port */ in mtk_smi_larb_config_port_gen1()
523 * m4u port, and we need to enable the aync clock for transform the smi in mtk_smi_common_probe()
/OK3568_Linux_fs/kernel/arch/arm64/boot/dts/mediatek/
H A Dmt2712e.dtsi327 compatible = "mediatek,mt2712-m4u";
344 compatible = "mediatek,mt2712-m4u";
H A Dmt8173.dtsi520 compatible = "mediatek,mt8173-m4u";
/OK3568_Linux_fs/kernel/sound/usb/
H A Dmidi.c1402 case USB_ID(0x0a92, 0x1020): /* ESI M4U */ in snd_usbmidi_out_endpoint_create()
/OK3568_Linux_fs/recovery/
HDrootfs.cpio.gz107070100A8AEB0000041ED0000000000000000000000116841B48100000000000000FD0000000200000000000000000000000200000000.�07070100A8B07C000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000900000000.gitkeep��07070100A8B07D000081A40000000000000000000000016841263500000000000000FD0000000200000000000000000000000B00000000.skip_fsck����07070100A8AEB10000A1FF0000000000000000000000016841B0B600000007000000FD0000000200000000000000000000000400000000bin���usr/bin�07070100A8B07E000081A400000000000000000000000168412635000001CC000000FD0000000200000000000000000000001100000000busybox. ...