Re: [PATCH V3 2/4] ARM: dts: rockchip: rk322x add iommu nodes

Am Montag, 24. Juli 2017, 10:32:08 CEST schrieb Simon Xue: > Add VPU/VDEC/VOP/IEP iommu nodes > > Signed-off-by: Simon Xue applied for 4.14 Thanks Heiko ___ iommu mailing list iommu@lists.linux-foundation.org

Re: [PATCH V3 4/4] ARM64: dts: rockchip: rk3399 add iommu nodes

Am Montag, 24. Juli 2017, 10:32:10 CEST schrieb Simon Xue: > Add VPU/VDEC/IEP/VOPL/VOPB/ISP0/ISP1 iommu nodes > > Signed-off-by: Simon Xue applied for 4.14 (after adapting the subject a bit, dropping the vop-mmus added via another patch) Thanks Heiko

Re: [PATCH v2 1/8] dt-bindings: mediatek: Add binding for mt2712 IOMMU and SMI

On Mon, Aug 21, 2017 at 07:00:14PM +0800, Yong Wu wrote: > This patch adds decriptions for mt2712 IOMMU and SMI. > > In order to balance the bandwidth, mt2712 has two M4Us, two > smi-commons, 10 smi-larbs. and mt2712 is also MTK IOMMU gen2 which > uses ARM Short-Descriptor translation table

Re: [PATCH V3 3/4] ARM64: dts: rockchip: rk3368 add iommu nodes

Am Montag, 24. Juli 2017, 10:32:09 CEST schrieb Simon Xue: > Add IEP/ISP/VOP/HEVC/VPU iommu nodes > > Signed-off-by: Simon Xue applied for 4.14 (after adapting the subject a bit) Thanks Heiko ___ iommu mailing list

Re: [PATCH V3 1/4] ARM64: dts: rockchip: rk3328 add iommu nodes

Am Montag, 24. Juli 2017, 10:32:07 CEST schrieb Simon Xue: > Add H265e/VEPU/VPU/VDEC/VOP iommu nodes > > Signed-off-by: Simon Xue applied for 4.14 (after adapting the subject a bit) Thanks Heiko ___ iommu mailing list

[PATCH v2 1/8] dt-bindings: mediatek: Add binding for mt2712 IOMMU and SMI

This patch adds decriptions for mt2712 IOMMU and SMI. In order to balance the bandwidth, mt2712 has two M4Us, two smi-commons, 10 smi-larbs. and mt2712 is also MTK IOMMU gen2 which uses ARM Short-Descriptor translation table format. The mt2712 M4U-SMI HW diagram is as below:

[PATCH v2 0/8] MT2712 IOMMU SUPPORT

This patchset mainly adds support for M4U of mt2712. The M4U in mt2712 is MTK's generation2 M4U which use the ARM Short-descriptor like mt8173. The main difference is that there are 2 M4Us and 2 smi-commons in mt2712, while there is only 1 M4U and 1 smi-common in mt8173. The purpose is for

[PATCH v2 3/8] iommu/mediatek: Add mt2712 IOMMU support

The M4U IP blocks in mt2712 is MTK's generation2 M4U which use the ARM Short-descriptor like mt8173, and most of the HW registers are the same. The difference is that there are 2 M4U HWs in mt2712 while there's only one in mt8173. The purpose of 2 M4U HWs is for balance the bandwidth. Normally

[PATCH v2 2/8] iommu/mediatek: Move MTK_M4U_TO_LARB/PORT into mtk_iommu.c

The definition of MTK_M4U_TO_LARB and MTK_M4U_TO_PORT are shared by all the gen2 M4U HWs. Thus, Move them out from mt8173-larb-port.h, and put them into the c file. Suggested-by: Honghui Zhang Signed-off-by: Yong Wu --- This patch only moves the

[PATCH v2 4/8] iommu/mediatek: Merge 2 M4U HWs into one iommu domain

In theory, If there are 2 M4U HWs, there should be 2 IOMMU domains. But one IOMMU domain(4GB iova range) is enough for us currently, It's unnecessary to maintain 2 pagetables. Besides, This patch can simplify our consumer code largely. They don't need map a iova range from one domain into

[PATCH v2 5/8] iommu/mediatek: Move pgtable allocation into domain_alloc

After adding the global list for M4U HW, We get a chance to move the pagetable allocation into the mtk_iommu_domain_alloc. Let the domain_alloc do the right thing. This patch is for fixing this problem[1]. [1]: https://patchwork.codeaurora.org/patch/53987/ Signed-off-by: Yong Wu

[PATCH v2 7/8] iommu/mediatek: Enlarge the validate PA range for 4GB mode

This patch is for 4GB mode, mainly for 4 issues: 1) Fix a 4GB bug: if the dram base is 0x4000_, the dram size is 0xc000_. then the code just meet a corner case because max_pfn is 0x10_. data->enable_4GB = !!(max_pfn > (0xUL >> PAGE_SHIFT)); It's true at the case

[PATCH v2 6/8] iommu/mediatek: Disable iommu clock when system suspend

When system suspend, infra power domain may be off, and the iommu's clock must be disabled when system off, or the iommu's bclk clock maybe disabled after system resume. Signed-off-by: Honghui Zhang Signed-off-by: Yong Wu ---

[PATCH v2 8/8] memory: mtk-smi: Degrade SMI init to module_init

The initialization of MediaTek power manager(SCPSYS) is builtin_platform_driver, and SMI must depend on power-domain. Thus, currently subsys_initcall for SMI is unnecessary, SMI will be always probe defered by power-domain. Degrade it to module_init. In addition, there are two small changes about

Re: [RFC 2/3] virtio-iommu: device probing and operations

On 21/08/17 08:59, Tian, Kevin wrote: >> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] >> Sent: Monday, April 24, 2017 11:06 PM >> 1. Attach device >> >> >> struct virtio_iommu_req_attach { >> le32address_space; >> le32

RE: [RFC 2/3] virtio-iommu: device probing and operations

> From: Jean-Philippe Brucker [mailto:jean-philippe.bruc...@arm.com] > Sent: Monday, April 24, 2017 11:06 PM > 1. Attach device > > > struct virtio_iommu_req_attach { > le32address_space; > le32device; > le32flags/reserved; >

Re: [PATCH 0/4] Patches to support ring0 SVM and devtlb

Thanks Joerg On Fri, Aug 18, 2017 at 11:35:21AM +0200, Joerg Roedel wrote: > Hi Ashok, > > On Tue, Aug 15, 2017 at 07:59:29AM -0700, Raj, Ashok wrote: > > I haven't received any update to this patchset.. > > > > Could you help get this merged through your tree? we have tested this > > series