Home
last modified time | relevance | path

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

/linux/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 through 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/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
/linux/arch/arm/boot/dts/mediatek/
H A Dmt7623n.dtsi104 compatible = "mediatek,mt7623-m4u",
105 "mediatek,mt2701-m4u";
H A Dmt2701.dtsi219 compatible = "mediatek,mt2701-m4u";
/linux/Documentation/devicetree/bindings/memory-controllers/
H A Dmediatek,smi-larb.yaml71 hardware id is not consecutive from its M4U point of view.
/linux/drivers/clk/mediatek/
H A Dclk-mt6735-infracfg.c37 GATE_MTK(CLK_INFRA_M4U, "m4u", "axi_sel", &infra_cg_regs, 8, &mtk_clk_gate_ops_setclr),
/linux/arch/arm64/boot/dts/mediatek/
H A Dmt2712e.dtsi327 compatible = "mediatek,mt2712-m4u";
345 compatible = "mediatek,mt2712-m4u";
/linux/sound/usb/
H A Dmidi.c1453 case USB_ID(0x0a92, 0x1020): /* ESI M4U */ in snd_usbmidi_out_endpoint_create()