Re: [PATCH v2 01/19] dt-bindings: mediatek: Add bindings for MT6779
From: chao hao <hidden>
Date: 2020-01-07 11:12:09
Also in:
linux-devicetree, linux-iommu, linux-mediatek, lkml
On Mon, 2020-01-06 at 15:57 -0600, Rob Herring wrote:
On Sun, 5 Jan 2020 18:45:05 +0800, Chao Hao wrote:quoted
This patch adds description for MT6779 IOMMU. MT6779 has two iommus, they are MM_IOMMU and APU_IOMMU which use ARM Short-Descriptor translation format. The MT6779 IOMMU hardware diagram is as below, it is only a brief diagram about iommu, it don't focus on the part of smi_larb, so I don't describe the smi_larb detailedly. EMI | -------------------------------------- | | MM_IOMMU APU_IOMMU | | SMI_COMMOM----------- APU_BUS | | | SMI_LARB(0~11) SMI_LARB12(FAKE) SMI_LARB13(FAKE) | | | | | -------------- | | | | | Multimedia engine CCU VPU MDLA EMDA All the connections are hardware fixed, software can not adjust it.quoted
From the diagram above, MM_IOMMU provides mapping for multimedia engine,but CCU is connected with smi_common directly, we can take them as larb12. APU_IOMMU provides mapping for APU engine, we can take them larb13. Larb12 and Larb13 are fake larbs. Signed-off-by: Chao Hao <redacted> --- .../bindings/iommu/mediatek,iommu.txt | 2 + include/dt-bindings/memory/mt6779-larb-port.h | 215 ++++++++++++++++++ 2 files changed, 217 insertions(+) create mode 100644 include/dt-bindings/memory/mt6779-larb-port.hPlease add Acked-by/Reviewed-by tags when posting new versions. However, there's no need to repost patches *only* to add the tags. The upstream maintainer will do that for acks received on the version they apply. If a tag was not added on purpose, please state why and what changed.
Hi Rob, I am Sorry, this is my first time upstream and not clear for some details, please forgive me for this mistake. I put the changed explanation into cover letter([PATCH v2 00/19] MT6779 IOMMU SUPPORT) about this patch. I will pay attention to this problem in next version. Change since v1 for this patch 1.Delete M4U_PORT_UNKNOWN define because of not use it. 2.Correct coding format: ex: /*larb3-VENC*/ --> /* larb3-VENC */ _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel