2019-05-27 06:55:21 +00:00
|
|
|
// SPDX-License-Identifier: GPL-2.0-only
|
2016-02-22 17:20:50 +00:00
|
|
|
/*
|
|
|
|
* Copyright (c) 2015-2016 MediaTek Inc.
|
|
|
|
* Author: Yong Wu <yong.wu@mediatek.com>
|
|
|
|
*/
|
2021-01-11 11:19:03 +00:00
|
|
|
#include <linux/bitfield.h>
|
2016-02-22 17:20:50 +00:00
|
|
|
#include <linux/bug.h>
|
|
|
|
#include <linux/clk.h>
|
|
|
|
#include <linux/component.h>
|
|
|
|
#include <linux/device.h>
|
2021-01-11 11:19:08 +00:00
|
|
|
#include <linux/dma-direct.h>
|
2016-02-22 17:20:50 +00:00
|
|
|
#include <linux/err.h>
|
|
|
|
#include <linux/interrupt.h>
|
|
|
|
#include <linux/io.h>
|
|
|
|
#include <linux/iommu.h>
|
|
|
|
#include <linux/iopoll.h>
|
|
|
|
#include <linux/list.h>
|
2020-09-04 10:40:38 +00:00
|
|
|
#include <linux/mfd/syscon.h>
|
2021-03-26 03:23:37 +00:00
|
|
|
#include <linux/module.h>
|
2016-02-22 17:20:50 +00:00
|
|
|
#include <linux/of_address.h>
|
|
|
|
#include <linux/of_irq.h>
|
|
|
|
#include <linux/of_platform.h>
|
|
|
|
#include <linux/platform_device.h>
|
2021-01-11 11:18:59 +00:00
|
|
|
#include <linux/pm_runtime.h>
|
2020-09-04 10:40:38 +00:00
|
|
|
#include <linux/regmap.h>
|
2016-02-22 17:20:50 +00:00
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/spinlock.h>
|
2020-09-04 10:40:38 +00:00
|
|
|
#include <linux/soc/mediatek/infracfg.h>
|
2016-02-22 17:20:50 +00:00
|
|
|
#include <asm/barrier.h>
|
|
|
|
#include <soc/mediatek/smi.h>
|
|
|
|
|
2016-06-08 09:50:58 +00:00
|
|
|
#include "mtk_iommu.h"
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
#define REG_MMU_PT_BASE_ADDR 0x000
|
2019-08-24 03:02:02 +00:00
|
|
|
#define MMU_PT_ADDR_MASK GENMASK(31, 7)
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
#define REG_MMU_INVALIDATE 0x020
|
|
|
|
#define F_ALL_INVLD 0x2
|
|
|
|
#define F_MMU_INV_RANGE 0x1
|
|
|
|
|
|
|
|
#define REG_MMU_INVLD_START_A 0x024
|
|
|
|
#define REG_MMU_INVLD_END_A 0x028
|
|
|
|
|
2020-07-03 04:41:27 +00:00
|
|
|
#define REG_MMU_INV_SEL_GEN2 0x02c
|
2020-07-03 04:41:22 +00:00
|
|
|
#define REG_MMU_INV_SEL_GEN1 0x038
|
2016-02-22 17:20:50 +00:00
|
|
|
#define F_INVLD_EN0 BIT(0)
|
|
|
|
#define F_INVLD_EN1 BIT(1)
|
|
|
|
|
2020-07-03 04:41:19 +00:00
|
|
|
#define REG_MMU_MISC_CTRL 0x048
|
2020-07-03 04:41:21 +00:00
|
|
|
#define F_MMU_IN_ORDER_WR_EN_MASK (BIT(1) | BIT(17))
|
|
|
|
#define F_MMU_STANDARD_AXI_MODE_MASK (BIT(3) | BIT(19))
|
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
#define REG_MMU_DCM_DIS 0x050
|
2020-07-03 04:41:24 +00:00
|
|
|
#define REG_MMU_WR_LEN_CTRL 0x054
|
|
|
|
#define F_MMU_WR_THROT_DIS_MASK (BIT(5) | BIT(21))
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
#define REG_MMU_CTRL_REG 0x110
|
2019-08-24 03:01:58 +00:00
|
|
|
#define F_MMU_TF_PROT_TO_PROGRAM_ADDR (2 << 4)
|
2016-02-22 17:20:50 +00:00
|
|
|
#define F_MMU_PREFETCH_RT_REPLACE_MOD BIT(4)
|
2019-08-24 03:01:58 +00:00
|
|
|
#define F_MMU_TF_PROT_TO_PROGRAM_ADDR_MT8173 (2 << 5)
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
#define REG_MMU_IVRP_PADDR 0x114
|
2018-03-18 01:52:54 +00:00
|
|
|
|
2017-08-21 11:00:20 +00:00
|
|
|
#define REG_MMU_VLD_PA_RNG 0x118
|
|
|
|
#define F_MMU_VLD_PA_RNG(EA, SA) (((EA) << 8) | (SA))
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
#define REG_MMU_INT_CONTROL0 0x120
|
|
|
|
#define F_L2_MULIT_HIT_EN BIT(0)
|
|
|
|
#define F_TABLE_WALK_FAULT_INT_EN BIT(1)
|
|
|
|
#define F_PREETCH_FIFO_OVERFLOW_INT_EN BIT(2)
|
|
|
|
#define F_MISS_FIFO_OVERFLOW_INT_EN BIT(3)
|
|
|
|
#define F_PREFETCH_FIFO_ERR_INT_EN BIT(5)
|
|
|
|
#define F_MISS_FIFO_ERR_INT_EN BIT(6)
|
|
|
|
#define F_INT_CLR_BIT BIT(12)
|
|
|
|
|
|
|
|
#define REG_MMU_INT_MAIN_CONTROL 0x124
|
2019-08-24 03:02:03 +00:00
|
|
|
/* mmu0 | mmu1 */
|
|
|
|
#define F_INT_TRANSLATION_FAULT (BIT(0) | BIT(7))
|
|
|
|
#define F_INT_MAIN_MULTI_HIT_FAULT (BIT(1) | BIT(8))
|
|
|
|
#define F_INT_INVALID_PA_FAULT (BIT(2) | BIT(9))
|
|
|
|
#define F_INT_ENTRY_REPLACEMENT_FAULT (BIT(3) | BIT(10))
|
|
|
|
#define F_INT_TLB_MISS_FAULT (BIT(4) | BIT(11))
|
|
|
|
#define F_INT_MISS_TRANSACTION_FIFO_FAULT (BIT(5) | BIT(12))
|
|
|
|
#define F_INT_PRETETCH_TRANSATION_FIFO_FAULT (BIT(6) | BIT(13))
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
#define REG_MMU_CPE_DONE 0x12C
|
|
|
|
|
|
|
|
#define REG_MMU_FAULT_ST1 0x134
|
2019-08-24 03:02:03 +00:00
|
|
|
#define F_REG_MMU0_FAULT_MASK GENMASK(6, 0)
|
|
|
|
#define F_REG_MMU1_FAULT_MASK GENMASK(13, 7)
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2019-08-24 03:02:03 +00:00
|
|
|
#define REG_MMU0_FAULT_VA 0x13c
|
2021-01-11 11:19:03 +00:00
|
|
|
#define F_MMU_INVAL_VA_31_12_MASK GENMASK(31, 12)
|
|
|
|
#define F_MMU_INVAL_VA_34_32_MASK GENMASK(11, 9)
|
|
|
|
#define F_MMU_INVAL_PA_34_32_MASK GENMASK(8, 6)
|
2016-02-22 17:20:50 +00:00
|
|
|
#define F_MMU_FAULT_VA_WRITE_BIT BIT(1)
|
|
|
|
#define F_MMU_FAULT_VA_LAYER_BIT BIT(0)
|
|
|
|
|
2019-08-24 03:02:03 +00:00
|
|
|
#define REG_MMU0_INVLD_PA 0x140
|
|
|
|
#define REG_MMU1_FAULT_VA 0x144
|
|
|
|
#define REG_MMU1_INVLD_PA 0x148
|
|
|
|
#define REG_MMU0_INT_ID 0x150
|
|
|
|
#define REG_MMU1_INT_ID 0x154
|
2020-07-03 04:41:23 +00:00
|
|
|
#define F_MMU_INT_ID_COMM_ID(a) (((a) >> 9) & 0x7)
|
|
|
|
#define F_MMU_INT_ID_SUB_COMM_ID(a) (((a) >> 7) & 0x3)
|
2019-08-24 03:02:03 +00:00
|
|
|
#define F_MMU_INT_ID_LARB_ID(a) (((a) >> 7) & 0x7)
|
|
|
|
#define F_MMU_INT_ID_PORT_ID(a) (((a) >> 2) & 0x1f)
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2020-07-03 04:41:25 +00:00
|
|
|
#define MTK_PROTECT_PA_ALIGN 256
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2020-07-03 04:41:20 +00:00
|
|
|
#define HAS_4GB_MODE BIT(0)
|
|
|
|
/* HW will use the EMI clock if there isn't the "bclk". */
|
|
|
|
#define HAS_BCLK BIT(1)
|
|
|
|
#define HAS_VLD_PA_RNG BIT(2)
|
|
|
|
#define RESET_AXI BIT(3)
|
2020-07-03 04:41:21 +00:00
|
|
|
#define OUT_ORDER_WR_EN BIT(4)
|
2020-07-03 04:41:23 +00:00
|
|
|
#define HAS_SUB_COMM BIT(5)
|
2020-07-03 04:41:24 +00:00
|
|
|
#define WR_THROT_EN BIT(6)
|
2020-09-07 10:16:48 +00:00
|
|
|
#define HAS_LEGACY_IVRP_PADDR BIT(7)
|
2021-01-11 11:18:55 +00:00
|
|
|
#define IOVA_34_EN BIT(8)
|
2020-07-03 04:41:20 +00:00
|
|
|
|
|
|
|
#define MTK_IOMMU_HAS_FLAG(pdata, _x) \
|
|
|
|
((((pdata)->flags) & (_x)) == (_x))
|
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
struct mtk_iommu_domain {
|
|
|
|
struct io_pgtable_cfg cfg;
|
|
|
|
struct io_pgtable_ops *iop;
|
|
|
|
|
2021-01-11 11:19:04 +00:00
|
|
|
struct mtk_iommu_data *data;
|
2016-02-22 17:20:50 +00:00
|
|
|
struct iommu_domain domain;
|
|
|
|
};
|
|
|
|
|
2018-10-18 11:13:38 +00:00
|
|
|
static const struct iommu_ops mtk_iommu_ops;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2021-01-11 11:18:57 +00:00
|
|
|
static int mtk_iommu_hw_init(const struct mtk_iommu_data *data);
|
|
|
|
|
2021-01-11 11:19:02 +00:00
|
|
|
#define MTK_IOMMU_TLB_ADDR(iova) ({ \
|
|
|
|
dma_addr_t _addr = iova; \
|
|
|
|
((lower_32_bits(_addr) & GENMASK(31, 12)) | upper_32_bits(_addr));\
|
|
|
|
})
|
|
|
|
|
2019-08-24 03:01:50 +00:00
|
|
|
/*
|
|
|
|
* In M4U 4GB mode, the physical address is remapped as below:
|
|
|
|
*
|
|
|
|
* CPU Physical address:
|
|
|
|
* ====================
|
|
|
|
*
|
|
|
|
* 0 1G 2G 3G 4G 5G
|
|
|
|
* |---A---|---B---|---C---|---D---|---E---|
|
|
|
|
* +--I/O--+------------Memory-------------+
|
|
|
|
*
|
|
|
|
* IOMMU output physical address:
|
|
|
|
* =============================
|
|
|
|
*
|
|
|
|
* 4G 5G 6G 7G 8G
|
|
|
|
* |---E---|---B---|---C---|---D---|
|
|
|
|
* +------------Memory-------------+
|
|
|
|
*
|
|
|
|
* The Region 'A'(I/O) can NOT be mapped by M4U; For Region 'B'/'C'/'D', the
|
|
|
|
* bit32 of the CPU physical address always is needed to set, and for Region
|
|
|
|
* 'E', the CPU physical address keep as is.
|
|
|
|
* Additionally, The iommu consumers always use the CPU phyiscal address.
|
|
|
|
*/
|
2019-08-24 03:01:55 +00:00
|
|
|
#define MTK_IOMMU_4GB_MODE_REMAP_BASE 0x140000000UL
|
2019-08-24 03:01:50 +00:00
|
|
|
|
2017-08-21 11:00:17 +00:00
|
|
|
static LIST_HEAD(m4ulist); /* List all the M4U HWs */
|
|
|
|
|
|
|
|
#define for_each_m4u(data) list_for_each_entry(data, &m4ulist, list)
|
|
|
|
|
2021-01-11 11:19:07 +00:00
|
|
|
struct mtk_iommu_iova_region {
|
|
|
|
dma_addr_t iova_base;
|
|
|
|
unsigned long long size;
|
|
|
|
};
|
|
|
|
|
|
|
|
static const struct mtk_iommu_iova_region single_domain[] = {
|
|
|
|
{.iova_base = 0, .size = SZ_4G},
|
|
|
|
};
|
|
|
|
|
2021-01-11 11:19:13 +00:00
|
|
|
static const struct mtk_iommu_iova_region mt8192_multi_dom[] = {
|
|
|
|
{ .iova_base = 0x0, .size = SZ_4G}, /* disp: 0 ~ 4G */
|
|
|
|
#if IS_ENABLED(CONFIG_ARCH_DMA_ADDR_T_64BIT)
|
|
|
|
{ .iova_base = SZ_4G, .size = SZ_4G}, /* vdec: 4G ~ 8G */
|
|
|
|
{ .iova_base = SZ_4G * 2, .size = SZ_4G}, /* CAM/MDP: 8G ~ 12G */
|
|
|
|
{ .iova_base = 0x240000000ULL, .size = 0x4000000}, /* CCU0 */
|
|
|
|
{ .iova_base = 0x244000000ULL, .size = 0x4000000}, /* CCU1 */
|
|
|
|
#endif
|
|
|
|
};
|
|
|
|
|
2017-08-21 11:00:17 +00:00
|
|
|
/*
|
|
|
|
* There may be 1 or 2 M4U HWs, But we always expect they are in the same domain
|
|
|
|
* for the performance.
|
|
|
|
*
|
|
|
|
* Here always return the mtk_iommu_data of the first probed M4U where the
|
|
|
|
* iommu domain information is recorded.
|
|
|
|
*/
|
|
|
|
static struct mtk_iommu_data *mtk_iommu_get_m4u_data(void)
|
|
|
|
{
|
|
|
|
struct mtk_iommu_data *data;
|
|
|
|
|
|
|
|
for_each_m4u(data)
|
|
|
|
return data;
|
|
|
|
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
static struct mtk_iommu_domain *to_mtk_domain(struct iommu_domain *dom)
|
|
|
|
{
|
|
|
|
return container_of(dom, struct mtk_iommu_domain, domain);
|
|
|
|
}
|
|
|
|
|
2021-01-07 12:29:09 +00:00
|
|
|
static void mtk_iommu_tlb_flush_all(struct mtk_iommu_data *data)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
2017-08-21 11:00:17 +00:00
|
|
|
for_each_m4u(data) {
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
if (pm_runtime_get_if_in_use(data->dev) <= 0)
|
|
|
|
continue;
|
|
|
|
|
2017-08-21 11:00:17 +00:00
|
|
|
writel_relaxed(F_INVLD_EN1 | F_INVLD_EN0,
|
2020-07-03 04:41:22 +00:00
|
|
|
data->base + data->plat_data->inv_sel_reg);
|
2017-08-21 11:00:17 +00:00
|
|
|
writel_relaxed(F_ALL_INVLD, data->base + REG_MMU_INVALIDATE);
|
|
|
|
wmb(); /* Make sure the tlb flush all done */
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
|
|
|
|
pm_runtime_put(data->dev);
|
2017-08-21 11:00:17 +00:00
|
|
|
}
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
2019-11-04 07:01:06 +00:00
|
|
|
static void mtk_iommu_tlb_flush_range_sync(unsigned long iova, size_t size,
|
2021-01-07 12:29:09 +00:00
|
|
|
size_t granule,
|
|
|
|
struct mtk_iommu_data *data)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
bool has_pm = !!data->dev->pm_domain;
|
2019-11-04 07:01:06 +00:00
|
|
|
unsigned long flags;
|
|
|
|
int ret;
|
|
|
|
u32 tmp;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2017-08-21 11:00:17 +00:00
|
|
|
for_each_m4u(data) {
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
if (has_pm) {
|
|
|
|
if (pm_runtime_get_if_in_use(data->dev) <= 0)
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
2019-11-04 07:01:06 +00:00
|
|
|
spin_lock_irqsave(&data->tlb_lock, flags);
|
2017-08-21 11:00:17 +00:00
|
|
|
writel_relaxed(F_INVLD_EN1 | F_INVLD_EN0,
|
2020-07-03 04:41:22 +00:00
|
|
|
data->base + data->plat_data->inv_sel_reg);
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2021-01-11 11:19:02 +00:00
|
|
|
writel_relaxed(MTK_IOMMU_TLB_ADDR(iova),
|
|
|
|
data->base + REG_MMU_INVLD_START_A);
|
|
|
|
writel_relaxed(MTK_IOMMU_TLB_ADDR(iova + size - 1),
|
2017-08-21 11:00:17 +00:00
|
|
|
data->base + REG_MMU_INVLD_END_A);
|
|
|
|
writel_relaxed(F_MMU_INV_RANGE,
|
|
|
|
data->base + REG_MMU_INVALIDATE);
|
2017-07-06 16:55:30 +00:00
|
|
|
|
2019-11-04 07:01:06 +00:00
|
|
|
/* tlb sync */
|
2017-08-21 11:00:17 +00:00
|
|
|
ret = readl_poll_timeout_atomic(data->base + REG_MMU_CPE_DONE,
|
2019-11-04 07:01:08 +00:00
|
|
|
tmp, tmp != 0, 10, 1000);
|
2017-08-21 11:00:17 +00:00
|
|
|
if (ret) {
|
|
|
|
dev_warn(data->dev,
|
|
|
|
"Partial TLB flush timed out, falling back to full flush\n");
|
2021-01-07 12:29:09 +00:00
|
|
|
mtk_iommu_tlb_flush_all(data);
|
2017-08-21 11:00:17 +00:00
|
|
|
}
|
|
|
|
/* Clear the CPE status */
|
|
|
|
writel_relaxed(0, data->base + REG_MMU_CPE_DONE);
|
2019-11-04 07:01:06 +00:00
|
|
|
spin_unlock_irqrestore(&data->tlb_lock, flags);
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
|
|
|
|
if (has_pm)
|
|
|
|
pm_runtime_put(data->dev);
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
static irqreturn_t mtk_iommu_isr(int irq, void *dev_id)
|
|
|
|
{
|
|
|
|
struct mtk_iommu_data *data = dev_id;
|
|
|
|
struct mtk_iommu_domain *dom = data->m4u_dom;
|
2020-07-03 04:41:23 +00:00
|
|
|
unsigned int fault_larb, fault_port, sub_comm = 0;
|
2021-01-11 11:19:03 +00:00
|
|
|
u32 int_state, regval, va34_32, pa34_32;
|
|
|
|
u64 fault_iova, fault_pa;
|
2016-02-22 17:20:50 +00:00
|
|
|
bool layer, write;
|
|
|
|
|
|
|
|
/* Read error info from registers */
|
|
|
|
int_state = readl_relaxed(data->base + REG_MMU_FAULT_ST1);
|
2019-08-24 03:02:03 +00:00
|
|
|
if (int_state & F_REG_MMU0_FAULT_MASK) {
|
|
|
|
regval = readl_relaxed(data->base + REG_MMU0_INT_ID);
|
|
|
|
fault_iova = readl_relaxed(data->base + REG_MMU0_FAULT_VA);
|
|
|
|
fault_pa = readl_relaxed(data->base + REG_MMU0_INVLD_PA);
|
|
|
|
} else {
|
|
|
|
regval = readl_relaxed(data->base + REG_MMU1_INT_ID);
|
|
|
|
fault_iova = readl_relaxed(data->base + REG_MMU1_FAULT_VA);
|
|
|
|
fault_pa = readl_relaxed(data->base + REG_MMU1_INVLD_PA);
|
|
|
|
}
|
2016-02-22 17:20:50 +00:00
|
|
|
layer = fault_iova & F_MMU_FAULT_VA_LAYER_BIT;
|
|
|
|
write = fault_iova & F_MMU_FAULT_VA_WRITE_BIT;
|
2021-01-11 11:19:03 +00:00
|
|
|
if (MTK_IOMMU_HAS_FLAG(data->plat_data, IOVA_34_EN)) {
|
|
|
|
va34_32 = FIELD_GET(F_MMU_INVAL_VA_34_32_MASK, fault_iova);
|
|
|
|
pa34_32 = FIELD_GET(F_MMU_INVAL_PA_34_32_MASK, fault_iova);
|
|
|
|
fault_iova = fault_iova & F_MMU_INVAL_VA_31_12_MASK;
|
|
|
|
fault_iova |= (u64)va34_32 << 32;
|
|
|
|
fault_pa |= (u64)pa34_32 << 32;
|
|
|
|
}
|
|
|
|
|
2019-08-24 03:02:03 +00:00
|
|
|
fault_port = F_MMU_INT_ID_PORT_ID(regval);
|
2020-07-03 04:41:23 +00:00
|
|
|
if (MTK_IOMMU_HAS_FLAG(data->plat_data, HAS_SUB_COMM)) {
|
|
|
|
fault_larb = F_MMU_INT_ID_COMM_ID(regval);
|
|
|
|
sub_comm = F_MMU_INT_ID_SUB_COMM_ID(regval);
|
|
|
|
} else {
|
|
|
|
fault_larb = F_MMU_INT_ID_LARB_ID(regval);
|
|
|
|
}
|
|
|
|
fault_larb = data->plat_data->larbid_remap[fault_larb][sub_comm];
|
2019-08-24 03:01:57 +00:00
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
if (report_iommu_fault(&dom->domain, data->dev, fault_iova,
|
|
|
|
write ? IOMMU_FAULT_WRITE : IOMMU_FAULT_READ)) {
|
|
|
|
dev_err_ratelimited(
|
|
|
|
data->dev,
|
2021-01-11 11:19:03 +00:00
|
|
|
"fault type=0x%x iova=0x%llx pa=0x%llx larb=%d port=%d layer=%d %s\n",
|
2016-02-22 17:20:50 +00:00
|
|
|
int_state, fault_iova, fault_pa, fault_larb, fault_port,
|
|
|
|
layer, write ? "write" : "read");
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Interrupt clear */
|
|
|
|
regval = readl_relaxed(data->base + REG_MMU_INT_CONTROL0);
|
|
|
|
regval |= F_INT_CLR_BIT;
|
|
|
|
writel_relaxed(regval, data->base + REG_MMU_INT_CONTROL0);
|
|
|
|
|
|
|
|
mtk_iommu_tlb_flush_all(data);
|
|
|
|
|
|
|
|
return IRQ_HANDLED;
|
|
|
|
}
|
|
|
|
|
2021-01-11 11:19:08 +00:00
|
|
|
static int mtk_iommu_get_domain_id(struct device *dev,
|
|
|
|
const struct mtk_iommu_plat_data *plat_data)
|
|
|
|
{
|
|
|
|
const struct mtk_iommu_iova_region *rgn = plat_data->iova_region;
|
|
|
|
const struct bus_dma_region *dma_rgn = dev->dma_range_map;
|
|
|
|
int i, candidate = -1;
|
|
|
|
dma_addr_t dma_end;
|
|
|
|
|
|
|
|
if (!dma_rgn || plat_data->iova_region_nr == 1)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
dma_end = dma_rgn->dma_start + dma_rgn->size - 1;
|
|
|
|
for (i = 0; i < plat_data->iova_region_nr; i++, rgn++) {
|
|
|
|
/* Best fit. */
|
|
|
|
if (dma_rgn->dma_start == rgn->iova_base &&
|
|
|
|
dma_end == rgn->iova_base + rgn->size - 1)
|
|
|
|
return i;
|
|
|
|
/* ok if it is inside this region. */
|
|
|
|
if (dma_rgn->dma_start >= rgn->iova_base &&
|
|
|
|
dma_end < rgn->iova_base + rgn->size)
|
|
|
|
candidate = i;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (candidate >= 0)
|
|
|
|
return candidate;
|
|
|
|
dev_err(dev, "Can NOT find the iommu domain id(%pad 0x%llx).\n",
|
|
|
|
&dma_rgn->dma_start, dma_rgn->size);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2021-01-11 11:19:11 +00:00
|
|
|
static void mtk_iommu_config(struct mtk_iommu_data *data, struct device *dev,
|
|
|
|
bool enable, unsigned int domid)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
|
|
|
struct mtk_smi_larb_iommu *larb_mmu;
|
|
|
|
unsigned int larbid, portid;
|
2018-11-29 13:01:00 +00:00
|
|
|
struct iommu_fwspec *fwspec = dev_iommu_fwspec_get(dev);
|
2021-01-11 11:19:11 +00:00
|
|
|
const struct mtk_iommu_iova_region *region;
|
2016-10-17 11:49:20 +00:00
|
|
|
int i;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2016-10-17 11:49:20 +00:00
|
|
|
for (i = 0; i < fwspec->num_ids; ++i) {
|
|
|
|
larbid = MTK_M4U_TO_LARB(fwspec->ids[i]);
|
|
|
|
portid = MTK_M4U_TO_PORT(fwspec->ids[i]);
|
2021-01-11 11:19:11 +00:00
|
|
|
|
2019-08-24 03:02:08 +00:00
|
|
|
larb_mmu = &data->larb_imu[larbid];
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2021-01-11 11:19:11 +00:00
|
|
|
region = data->plat_data->iova_region + domid;
|
|
|
|
larb_mmu->bank[portid] = upper_32_bits(region->iova_base);
|
|
|
|
|
|
|
|
dev_dbg(dev, "%s iommu for larb(%s) port %d dom %d bank %d.\n",
|
|
|
|
enable ? "enable" : "disable", dev_name(larb_mmu->dev),
|
|
|
|
portid, domid, larb_mmu->bank[portid]);
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
if (enable)
|
|
|
|
larb_mmu->mmu |= MTK_SMI_MMU_EN(portid);
|
|
|
|
else
|
|
|
|
larb_mmu->mmu &= ~MTK_SMI_MMU_EN(portid);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2021-01-11 11:19:05 +00:00
|
|
|
static int mtk_iommu_domain_finalise(struct mtk_iommu_domain *dom,
|
2021-01-11 11:19:09 +00:00
|
|
|
struct mtk_iommu_data *data,
|
|
|
|
unsigned int domid)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
2021-01-11 11:19:09 +00:00
|
|
|
const struct mtk_iommu_iova_region *region;
|
|
|
|
|
|
|
|
/* Use the exist domain as there is only one pgtable here. */
|
|
|
|
if (data->m4u_dom) {
|
|
|
|
dom->iop = data->m4u_dom->iop;
|
|
|
|
dom->cfg = data->m4u_dom->cfg;
|
|
|
|
dom->domain.pgsize_bitmap = data->m4u_dom->cfg.pgsize_bitmap;
|
|
|
|
goto update_iova_region;
|
|
|
|
}
|
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
dom->cfg = (struct io_pgtable_cfg) {
|
|
|
|
.quirks = IO_PGTABLE_QUIRK_ARM_NS |
|
|
|
|
IO_PGTABLE_QUIRK_NO_PERMS |
|
2019-08-24 03:01:55 +00:00
|
|
|
IO_PGTABLE_QUIRK_ARM_MTK_EXT,
|
2016-02-22 17:20:50 +00:00
|
|
|
.pgsize_bitmap = mtk_iommu_ops.pgsize_bitmap,
|
2021-01-11 11:18:55 +00:00
|
|
|
.ias = MTK_IOMMU_HAS_FLAG(data->plat_data, IOVA_34_EN) ? 34 : 32,
|
2016-02-22 17:20:50 +00:00
|
|
|
.iommu_dev = data->dev,
|
|
|
|
};
|
|
|
|
|
2021-01-11 11:18:56 +00:00
|
|
|
if (MTK_IOMMU_HAS_FLAG(data->plat_data, HAS_4GB_MODE))
|
|
|
|
dom->cfg.oas = data->enable_4GB ? 33 : 32;
|
|
|
|
else
|
|
|
|
dom->cfg.oas = 35;
|
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
dom->iop = alloc_io_pgtable_ops(ARM_V7S, &dom->cfg, data);
|
|
|
|
if (!dom->iop) {
|
|
|
|
dev_err(data->dev, "Failed to alloc io pgtable\n");
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Update our support page sizes bitmap */
|
2016-04-07 17:42:06 +00:00
|
|
|
dom->domain.pgsize_bitmap = dom->cfg.pgsize_bitmap;
|
2021-01-11 11:19:06 +00:00
|
|
|
|
2021-01-11 11:19:09 +00:00
|
|
|
update_iova_region:
|
|
|
|
/* Update the iova region for this domain */
|
|
|
|
region = data->plat_data->iova_region + domid;
|
|
|
|
dom->domain.geometry.aperture_start = region->iova_base;
|
|
|
|
dom->domain.geometry.aperture_end = region->iova_base + region->size - 1;
|
2021-01-11 11:19:06 +00:00
|
|
|
dom->domain.geometry.force_aperture = true;
|
2016-02-22 17:20:50 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static struct iommu_domain *mtk_iommu_domain_alloc(unsigned type)
|
|
|
|
{
|
|
|
|
struct mtk_iommu_domain *dom;
|
|
|
|
|
|
|
|
if (type != IOMMU_DOMAIN_DMA)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
dom = kzalloc(sizeof(*dom), GFP_KERNEL);
|
|
|
|
if (!dom)
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
return &dom->domain;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void mtk_iommu_domain_free(struct iommu_domain *domain)
|
|
|
|
{
|
|
|
|
kfree(to_mtk_domain(domain));
|
|
|
|
}
|
|
|
|
|
|
|
|
static int mtk_iommu_attach_device(struct iommu_domain *domain,
|
|
|
|
struct device *dev)
|
|
|
|
{
|
2022-05-03 07:13:55 +00:00
|
|
|
struct mtk_iommu_data *data = dev_iommu_priv_get(dev), *frstdata;
|
2016-02-22 17:20:50 +00:00
|
|
|
struct mtk_iommu_domain *dom = to_mtk_domain(domain);
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
struct device *m4udev = data->dev;
|
2021-01-11 11:19:08 +00:00
|
|
|
int ret, domid;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2021-01-11 11:19:08 +00:00
|
|
|
domid = mtk_iommu_get_domain_id(dev, data->plat_data);
|
|
|
|
if (domid < 0)
|
|
|
|
return domid;
|
|
|
|
|
2021-01-11 11:19:05 +00:00
|
|
|
if (!dom->data) {
|
2022-05-03 07:13:55 +00:00
|
|
|
/* Data is in the frstdata in sharing pgtable case. */
|
|
|
|
frstdata = mtk_iommu_get_m4u_data();
|
|
|
|
|
|
|
|
if (mtk_iommu_domain_finalise(dom, frstdata, domid))
|
2021-01-11 11:19:05 +00:00
|
|
|
return -ENODEV;
|
|
|
|
dom->data = data;
|
|
|
|
}
|
|
|
|
|
2022-05-03 07:13:58 +00:00
|
|
|
mutex_lock(&data->mutex);
|
2021-01-11 11:18:57 +00:00
|
|
|
if (!data->m4u_dom) { /* Initialize the M4U HW */
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
ret = pm_runtime_resume_and_get(m4udev);
|
|
|
|
if (ret < 0)
|
2022-05-03 07:13:58 +00:00
|
|
|
goto err_unlock;
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
|
2021-01-11 11:18:57 +00:00
|
|
|
ret = mtk_iommu_hw_init(data);
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
if (ret) {
|
|
|
|
pm_runtime_put(m4udev);
|
2022-05-03 07:13:58 +00:00
|
|
|
goto err_unlock;
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
}
|
2016-02-22 17:20:50 +00:00
|
|
|
data->m4u_dom = dom;
|
2019-10-25 18:08:37 +00:00
|
|
|
writel(dom->cfg.arm_v7s_cfg.ttbr & MMU_PT_ADDR_MASK,
|
2017-08-21 11:00:18 +00:00
|
|
|
data->base + REG_MMU_PT_BASE_ADDR);
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
|
|
|
|
pm_runtime_put(m4udev);
|
2017-08-21 11:00:17 +00:00
|
|
|
}
|
2022-05-03 07:13:58 +00:00
|
|
|
mutex_unlock(&data->mutex);
|
2017-08-21 11:00:17 +00:00
|
|
|
|
2021-01-11 11:19:11 +00:00
|
|
|
mtk_iommu_config(data, dev, true, domid);
|
2016-02-22 17:20:50 +00:00
|
|
|
return 0;
|
2022-05-03 07:13:58 +00:00
|
|
|
|
|
|
|
err_unlock:
|
|
|
|
mutex_unlock(&data->mutex);
|
|
|
|
return ret;
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static void mtk_iommu_detach_device(struct iommu_domain *domain,
|
|
|
|
struct device *dev)
|
|
|
|
{
|
2020-03-26 15:08:38 +00:00
|
|
|
struct mtk_iommu_data *data = dev_iommu_priv_get(dev);
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2021-01-11 11:19:11 +00:00
|
|
|
mtk_iommu_config(data, dev, false, 0);
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static int mtk_iommu_map(struct iommu_domain *domain, unsigned long iova,
|
2019-09-08 16:56:38 +00:00
|
|
|
phys_addr_t paddr, size_t size, int prot, gfp_t gfp)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
|
|
|
struct mtk_iommu_domain *dom = to_mtk_domain(domain);
|
|
|
|
|
2019-08-24 03:01:55 +00:00
|
|
|
/* The "4GB mode" M4U physically can not use the lower remap of Dram. */
|
2021-01-11 11:19:04 +00:00
|
|
|
if (dom->data->enable_4GB)
|
2019-08-24 03:01:55 +00:00
|
|
|
paddr |= BIT_ULL(32);
|
|
|
|
|
2019-11-04 07:01:07 +00:00
|
|
|
/* Synchronize with the tlb_lock */
|
2020-06-12 03:39:55 +00:00
|
|
|
return dom->iop->map(dom->iop, iova, paddr, size, prot, gfp);
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static size_t mtk_iommu_unmap(struct iommu_domain *domain,
|
2019-07-02 15:44:06 +00:00
|
|
|
unsigned long iova, size_t size,
|
|
|
|
struct iommu_iotlb_gather *gather)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
|
|
|
struct mtk_iommu_domain *dom = to_mtk_domain(domain);
|
|
|
|
|
2021-07-23 09:32:05 +00:00
|
|
|
iommu_iotlb_gather_add_range(gather, iova, size);
|
2019-11-04 07:01:07 +00:00
|
|
|
return dom->iop->unmap(dom->iop, iova, size, gather);
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
2019-07-02 15:44:06 +00:00
|
|
|
static void mtk_iommu_flush_iotlb_all(struct iommu_domain *domain)
|
|
|
|
{
|
2021-01-11 11:19:04 +00:00
|
|
|
struct mtk_iommu_domain *dom = to_mtk_domain(domain);
|
|
|
|
|
|
|
|
mtk_iommu_tlb_flush_all(dom->data);
|
2019-07-02 15:44:06 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static void mtk_iommu_iotlb_sync(struct iommu_domain *domain,
|
|
|
|
struct iommu_iotlb_gather *gather)
|
2017-09-28 14:55:02 +00:00
|
|
|
{
|
2021-01-11 11:19:04 +00:00
|
|
|
struct mtk_iommu_domain *dom = to_mtk_domain(domain);
|
2021-01-07 12:29:06 +00:00
|
|
|
size_t length = gather->end - gather->start + 1;
|
2019-11-04 07:01:03 +00:00
|
|
|
|
2019-11-04 07:01:06 +00:00
|
|
|
mtk_iommu_tlb_flush_range_sync(gather->start, length, gather->pgsize,
|
2021-01-11 11:19:04 +00:00
|
|
|
dom->data);
|
2017-09-28 14:55:02 +00:00
|
|
|
}
|
|
|
|
|
2021-01-07 12:29:05 +00:00
|
|
|
static void mtk_iommu_sync_map(struct iommu_domain *domain, unsigned long iova,
|
|
|
|
size_t size)
|
|
|
|
{
|
2021-01-11 11:19:04 +00:00
|
|
|
struct mtk_iommu_domain *dom = to_mtk_domain(domain);
|
2021-01-07 12:29:05 +00:00
|
|
|
|
2021-01-11 11:19:04 +00:00
|
|
|
mtk_iommu_tlb_flush_range_sync(iova, size, size, dom->data);
|
2021-01-07 12:29:05 +00:00
|
|
|
}
|
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
static phys_addr_t mtk_iommu_iova_to_phys(struct iommu_domain *domain,
|
|
|
|
dma_addr_t iova)
|
|
|
|
{
|
|
|
|
struct mtk_iommu_domain *dom = to_mtk_domain(domain);
|
|
|
|
phys_addr_t pa;
|
|
|
|
|
|
|
|
pa = dom->iop->iova_to_phys(dom->iop, iova);
|
2021-09-27 12:18:44 +00:00
|
|
|
if (IS_ENABLED(CONFIG_PHYS_ADDR_T_64BIT) &&
|
|
|
|
dom->data->enable_4GB &&
|
|
|
|
pa >= MTK_IOMMU_4GB_MODE_REMAP_BASE)
|
2019-08-24 03:01:55 +00:00
|
|
|
pa &= ~BIT_ULL(32);
|
2017-08-21 11:00:20 +00:00
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
return pa;
|
|
|
|
}
|
|
|
|
|
2020-04-29 13:37:00 +00:00
|
|
|
static struct iommu_device *mtk_iommu_probe_device(struct device *dev)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
2018-11-29 13:01:00 +00:00
|
|
|
struct iommu_fwspec *fwspec = dev_iommu_fwspec_get(dev);
|
2017-02-03 11:57:32 +00:00
|
|
|
struct mtk_iommu_data *data;
|
media: iommu/mediatek: Add device_link between the consumer and the larb devices
[ Upstream commit 635319a4a7444ca97124d781cd96deb277ff4d40 ]
MediaTek IOMMU-SMI diagram is like below. all the consumer connect with
smi-larb, then connect with smi-common.
M4U
|
smi-common
|
-------------
| | ...
| |
larb1 larb2
| |
vdec venc
When the consumer works, it should enable the smi-larb's power which
also need enable the smi-common's power firstly.
Thus, First of all, use the device link connect the consumer and the
smi-larbs. then add device link between the smi-larb and smi-common.
This patch adds device_link between the consumer and the larbs.
When device_link_add, I add the flag DL_FLAG_STATELESS to avoid calling
pm_runtime_xx to keep the original status of clocks. It can avoid two
issues:
1) Display HW show fastlogo abnormally reported in [1]. At the beggining,
all the clocks are enabled before entering kernel, but the clocks for
display HW(always in larb0) will be gated after clk_enable and clk_disable
called from device_link_add(->pm_runtime_resume) and rpm_idle. The clock
operation happened before display driver probe. At that time, the display
HW will be abnormal.
2) A deadlock issue reported in [2]. Use DL_FLAG_STATELESS to skip
pm_runtime_xx to avoid the deadlock.
Corresponding, DL_FLAG_AUTOREMOVE_CONSUMER can't be added, then
device_link_removed should be added explicitly.
Meanwhile, Currently we don't have a device connect with 2 larbs at the
same time. Disallow this case, print the error log.
[1] https://lore.kernel.org/linux-mediatek/1564213888.22908.4.camel@mhfsdcap03/
[2] https://lore.kernel.org/patchwork/patch/1086569/
Suggested-by: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Tested-by: Frank Wunderlich <frank-w@public-files.de> # BPI-R2/MT7623
Acked-by: Joerg Roedel <jroedel@suse.de>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2022-01-17 07:05:02 +00:00
|
|
|
struct device_link *link;
|
|
|
|
struct device *larbdev;
|
|
|
|
unsigned int larbid, larbidx, i;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2018-11-29 13:01:00 +00:00
|
|
|
if (!fwspec || fwspec->ops != &mtk_iommu_ops)
|
2020-04-29 13:37:00 +00:00
|
|
|
return ERR_PTR(-ENODEV); /* Not a iommu client device */
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2020-03-26 15:08:38 +00:00
|
|
|
data = dev_iommu_priv_get(dev);
|
2017-02-03 11:57:32 +00:00
|
|
|
|
media: iommu/mediatek: Add device_link between the consumer and the larb devices
[ Upstream commit 635319a4a7444ca97124d781cd96deb277ff4d40 ]
MediaTek IOMMU-SMI diagram is like below. all the consumer connect with
smi-larb, then connect with smi-common.
M4U
|
smi-common
|
-------------
| | ...
| |
larb1 larb2
| |
vdec venc
When the consumer works, it should enable the smi-larb's power which
also need enable the smi-common's power firstly.
Thus, First of all, use the device link connect the consumer and the
smi-larbs. then add device link between the smi-larb and smi-common.
This patch adds device_link between the consumer and the larbs.
When device_link_add, I add the flag DL_FLAG_STATELESS to avoid calling
pm_runtime_xx to keep the original status of clocks. It can avoid two
issues:
1) Display HW show fastlogo abnormally reported in [1]. At the beggining,
all the clocks are enabled before entering kernel, but the clocks for
display HW(always in larb0) will be gated after clk_enable and clk_disable
called from device_link_add(->pm_runtime_resume) and rpm_idle. The clock
operation happened before display driver probe. At that time, the display
HW will be abnormal.
2) A deadlock issue reported in [2]. Use DL_FLAG_STATELESS to skip
pm_runtime_xx to avoid the deadlock.
Corresponding, DL_FLAG_AUTOREMOVE_CONSUMER can't be added, then
device_link_removed should be added explicitly.
Meanwhile, Currently we don't have a device connect with 2 larbs at the
same time. Disallow this case, print the error log.
[1] https://lore.kernel.org/linux-mediatek/1564213888.22908.4.camel@mhfsdcap03/
[2] https://lore.kernel.org/patchwork/patch/1086569/
Suggested-by: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Tested-by: Frank Wunderlich <frank-w@public-files.de> # BPI-R2/MT7623
Acked-by: Joerg Roedel <jroedel@suse.de>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2022-01-17 07:05:02 +00:00
|
|
|
/*
|
|
|
|
* Link the consumer device with the smi-larb device(supplier).
|
|
|
|
* The device that connects with each a larb is a independent HW.
|
|
|
|
* All the ports in each a device should be in the same larbs.
|
|
|
|
*/
|
|
|
|
larbid = MTK_M4U_TO_LARB(fwspec->ids[0]);
|
2022-05-05 13:27:30 +00:00
|
|
|
if (larbid >= MTK_LARB_NR_MAX)
|
|
|
|
return ERR_PTR(-EINVAL);
|
|
|
|
|
media: iommu/mediatek: Add device_link between the consumer and the larb devices
[ Upstream commit 635319a4a7444ca97124d781cd96deb277ff4d40 ]
MediaTek IOMMU-SMI diagram is like below. all the consumer connect with
smi-larb, then connect with smi-common.
M4U
|
smi-common
|
-------------
| | ...
| |
larb1 larb2
| |
vdec venc
When the consumer works, it should enable the smi-larb's power which
also need enable the smi-common's power firstly.
Thus, First of all, use the device link connect the consumer and the
smi-larbs. then add device link between the smi-larb and smi-common.
This patch adds device_link between the consumer and the larbs.
When device_link_add, I add the flag DL_FLAG_STATELESS to avoid calling
pm_runtime_xx to keep the original status of clocks. It can avoid two
issues:
1) Display HW show fastlogo abnormally reported in [1]. At the beggining,
all the clocks are enabled before entering kernel, but the clocks for
display HW(always in larb0) will be gated after clk_enable and clk_disable
called from device_link_add(->pm_runtime_resume) and rpm_idle. The clock
operation happened before display driver probe. At that time, the display
HW will be abnormal.
2) A deadlock issue reported in [2]. Use DL_FLAG_STATELESS to skip
pm_runtime_xx to avoid the deadlock.
Corresponding, DL_FLAG_AUTOREMOVE_CONSUMER can't be added, then
device_link_removed should be added explicitly.
Meanwhile, Currently we don't have a device connect with 2 larbs at the
same time. Disallow this case, print the error log.
[1] https://lore.kernel.org/linux-mediatek/1564213888.22908.4.camel@mhfsdcap03/
[2] https://lore.kernel.org/patchwork/patch/1086569/
Suggested-by: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Tested-by: Frank Wunderlich <frank-w@public-files.de> # BPI-R2/MT7623
Acked-by: Joerg Roedel <jroedel@suse.de>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2022-01-17 07:05:02 +00:00
|
|
|
for (i = 1; i < fwspec->num_ids; i++) {
|
|
|
|
larbidx = MTK_M4U_TO_LARB(fwspec->ids[i]);
|
|
|
|
if (larbid != larbidx) {
|
|
|
|
dev_err(dev, "Can only use one larb. Fail@larb%d-%d.\n",
|
|
|
|
larbid, larbidx);
|
|
|
|
return ERR_PTR(-EINVAL);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
larbdev = data->larb_imu[larbid].dev;
|
2022-05-05 13:27:30 +00:00
|
|
|
if (!larbdev)
|
|
|
|
return ERR_PTR(-EINVAL);
|
|
|
|
|
media: iommu/mediatek: Add device_link between the consumer and the larb devices
[ Upstream commit 635319a4a7444ca97124d781cd96deb277ff4d40 ]
MediaTek IOMMU-SMI diagram is like below. all the consumer connect with
smi-larb, then connect with smi-common.
M4U
|
smi-common
|
-------------
| | ...
| |
larb1 larb2
| |
vdec venc
When the consumer works, it should enable the smi-larb's power which
also need enable the smi-common's power firstly.
Thus, First of all, use the device link connect the consumer and the
smi-larbs. then add device link between the smi-larb and smi-common.
This patch adds device_link between the consumer and the larbs.
When device_link_add, I add the flag DL_FLAG_STATELESS to avoid calling
pm_runtime_xx to keep the original status of clocks. It can avoid two
issues:
1) Display HW show fastlogo abnormally reported in [1]. At the beggining,
all the clocks are enabled before entering kernel, but the clocks for
display HW(always in larb0) will be gated after clk_enable and clk_disable
called from device_link_add(->pm_runtime_resume) and rpm_idle. The clock
operation happened before display driver probe. At that time, the display
HW will be abnormal.
2) A deadlock issue reported in [2]. Use DL_FLAG_STATELESS to skip
pm_runtime_xx to avoid the deadlock.
Corresponding, DL_FLAG_AUTOREMOVE_CONSUMER can't be added, then
device_link_removed should be added explicitly.
Meanwhile, Currently we don't have a device connect with 2 larbs at the
same time. Disallow this case, print the error log.
[1] https://lore.kernel.org/linux-mediatek/1564213888.22908.4.camel@mhfsdcap03/
[2] https://lore.kernel.org/patchwork/patch/1086569/
Suggested-by: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Tested-by: Frank Wunderlich <frank-w@public-files.de> # BPI-R2/MT7623
Acked-by: Joerg Roedel <jroedel@suse.de>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2022-01-17 07:05:02 +00:00
|
|
|
link = device_link_add(dev, larbdev,
|
|
|
|
DL_FLAG_PM_RUNTIME | DL_FLAG_STATELESS);
|
|
|
|
if (!link)
|
|
|
|
dev_err(dev, "Unable to link %s\n", dev_name(larbdev));
|
2020-04-29 13:37:00 +00:00
|
|
|
return &data->iommu;
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
2020-04-29 13:37:00 +00:00
|
|
|
static void mtk_iommu_release_device(struct device *dev)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
2018-11-29 13:01:00 +00:00
|
|
|
struct iommu_fwspec *fwspec = dev_iommu_fwspec_get(dev);
|
media: iommu/mediatek: Add device_link between the consumer and the larb devices
[ Upstream commit 635319a4a7444ca97124d781cd96deb277ff4d40 ]
MediaTek IOMMU-SMI diagram is like below. all the consumer connect with
smi-larb, then connect with smi-common.
M4U
|
smi-common
|
-------------
| | ...
| |
larb1 larb2
| |
vdec venc
When the consumer works, it should enable the smi-larb's power which
also need enable the smi-common's power firstly.
Thus, First of all, use the device link connect the consumer and the
smi-larbs. then add device link between the smi-larb and smi-common.
This patch adds device_link between the consumer and the larbs.
When device_link_add, I add the flag DL_FLAG_STATELESS to avoid calling
pm_runtime_xx to keep the original status of clocks. It can avoid two
issues:
1) Display HW show fastlogo abnormally reported in [1]. At the beggining,
all the clocks are enabled before entering kernel, but the clocks for
display HW(always in larb0) will be gated after clk_enable and clk_disable
called from device_link_add(->pm_runtime_resume) and rpm_idle. The clock
operation happened before display driver probe. At that time, the display
HW will be abnormal.
2) A deadlock issue reported in [2]. Use DL_FLAG_STATELESS to skip
pm_runtime_xx to avoid the deadlock.
Corresponding, DL_FLAG_AUTOREMOVE_CONSUMER can't be added, then
device_link_removed should be added explicitly.
Meanwhile, Currently we don't have a device connect with 2 larbs at the
same time. Disallow this case, print the error log.
[1] https://lore.kernel.org/linux-mediatek/1564213888.22908.4.camel@mhfsdcap03/
[2] https://lore.kernel.org/patchwork/patch/1086569/
Suggested-by: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Tested-by: Frank Wunderlich <frank-w@public-files.de> # BPI-R2/MT7623
Acked-by: Joerg Roedel <jroedel@suse.de>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2022-01-17 07:05:02 +00:00
|
|
|
struct mtk_iommu_data *data;
|
|
|
|
struct device *larbdev;
|
|
|
|
unsigned int larbid;
|
2017-02-03 11:57:32 +00:00
|
|
|
|
2018-11-29 13:01:00 +00:00
|
|
|
if (!fwspec || fwspec->ops != &mtk_iommu_ops)
|
2016-02-22 17:20:50 +00:00
|
|
|
return;
|
|
|
|
|
media: iommu/mediatek: Add device_link between the consumer and the larb devices
[ Upstream commit 635319a4a7444ca97124d781cd96deb277ff4d40 ]
MediaTek IOMMU-SMI diagram is like below. all the consumer connect with
smi-larb, then connect with smi-common.
M4U
|
smi-common
|
-------------
| | ...
| |
larb1 larb2
| |
vdec venc
When the consumer works, it should enable the smi-larb's power which
also need enable the smi-common's power firstly.
Thus, First of all, use the device link connect the consumer and the
smi-larbs. then add device link between the smi-larb and smi-common.
This patch adds device_link between the consumer and the larbs.
When device_link_add, I add the flag DL_FLAG_STATELESS to avoid calling
pm_runtime_xx to keep the original status of clocks. It can avoid two
issues:
1) Display HW show fastlogo abnormally reported in [1]. At the beggining,
all the clocks are enabled before entering kernel, but the clocks for
display HW(always in larb0) will be gated after clk_enable and clk_disable
called from device_link_add(->pm_runtime_resume) and rpm_idle. The clock
operation happened before display driver probe. At that time, the display
HW will be abnormal.
2) A deadlock issue reported in [2]. Use DL_FLAG_STATELESS to skip
pm_runtime_xx to avoid the deadlock.
Corresponding, DL_FLAG_AUTOREMOVE_CONSUMER can't be added, then
device_link_removed should be added explicitly.
Meanwhile, Currently we don't have a device connect with 2 larbs at the
same time. Disallow this case, print the error log.
[1] https://lore.kernel.org/linux-mediatek/1564213888.22908.4.camel@mhfsdcap03/
[2] https://lore.kernel.org/patchwork/patch/1086569/
Suggested-by: Tomasz Figa <tfiga@chromium.org>
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Tested-by: Frank Wunderlich <frank-w@public-files.de> # BPI-R2/MT7623
Acked-by: Joerg Roedel <jroedel@suse.de>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
2022-01-17 07:05:02 +00:00
|
|
|
data = dev_iommu_priv_get(dev);
|
|
|
|
larbid = MTK_M4U_TO_LARB(fwspec->ids[0]);
|
|
|
|
larbdev = data->larb_imu[larbid].dev;
|
|
|
|
device_link_remove(dev, larbdev);
|
|
|
|
|
2016-10-17 11:49:20 +00:00
|
|
|
iommu_fwspec_free(dev);
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static struct iommu_group *mtk_iommu_device_group(struct device *dev)
|
|
|
|
{
|
2017-08-21 11:00:17 +00:00
|
|
|
struct mtk_iommu_data *data = mtk_iommu_get_m4u_data();
|
2021-01-11 11:19:09 +00:00
|
|
|
struct iommu_group *group;
|
2021-01-11 11:19:08 +00:00
|
|
|
int domid;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2016-10-17 11:49:20 +00:00
|
|
|
if (!data)
|
2016-02-22 17:20:50 +00:00
|
|
|
return ERR_PTR(-ENODEV);
|
|
|
|
|
2021-01-11 11:19:08 +00:00
|
|
|
domid = mtk_iommu_get_domain_id(dev, data->plat_data);
|
|
|
|
if (domid < 0)
|
|
|
|
return ERR_PTR(domid);
|
|
|
|
|
2022-05-03 07:13:58 +00:00
|
|
|
mutex_lock(&data->mutex);
|
2021-01-11 11:19:09 +00:00
|
|
|
group = data->m4u_group[domid];
|
|
|
|
if (!group) {
|
|
|
|
group = iommu_group_alloc();
|
|
|
|
if (!IS_ERR(group))
|
|
|
|
data->m4u_group[domid] = group;
|
2016-11-11 17:59:24 +00:00
|
|
|
} else {
|
2021-01-11 11:19:09 +00:00
|
|
|
iommu_group_ref_get(group);
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
2022-05-03 07:13:58 +00:00
|
|
|
mutex_unlock(&data->mutex);
|
2021-01-11 11:19:09 +00:00
|
|
|
return group;
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static int mtk_iommu_of_xlate(struct device *dev, struct of_phandle_args *args)
|
|
|
|
{
|
|
|
|
struct platform_device *m4updev;
|
|
|
|
|
|
|
|
if (args->args_count != 1) {
|
|
|
|
dev_err(dev, "invalid #iommu-cells(%d) property for IOMMU\n",
|
|
|
|
args->args_count);
|
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
|
2020-03-26 15:08:38 +00:00
|
|
|
if (!dev_iommu_priv_get(dev)) {
|
2016-02-22 17:20:50 +00:00
|
|
|
/* Get the m4u device */
|
|
|
|
m4updev = of_find_device_by_node(args->np);
|
|
|
|
if (WARN_ON(!m4updev))
|
|
|
|
return -EINVAL;
|
|
|
|
|
2020-03-26 15:08:38 +00:00
|
|
|
dev_iommu_priv_set(dev, platform_get_drvdata(m4updev));
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
2016-10-17 11:49:20 +00:00
|
|
|
return iommu_fwspec_add_ids(dev, args->args, 1);
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
2021-01-11 11:19:10 +00:00
|
|
|
static void mtk_iommu_get_resv_regions(struct device *dev,
|
|
|
|
struct list_head *head)
|
|
|
|
{
|
|
|
|
struct mtk_iommu_data *data = dev_iommu_priv_get(dev);
|
|
|
|
unsigned int domid = mtk_iommu_get_domain_id(dev, data->plat_data), i;
|
|
|
|
const struct mtk_iommu_iova_region *resv, *curdom;
|
|
|
|
struct iommu_resv_region *region;
|
|
|
|
int prot = IOMMU_WRITE | IOMMU_READ;
|
|
|
|
|
2021-02-04 15:00:01 +00:00
|
|
|
if ((int)domid < 0)
|
2021-01-11 11:19:10 +00:00
|
|
|
return;
|
|
|
|
curdom = data->plat_data->iova_region + domid;
|
|
|
|
for (i = 0; i < data->plat_data->iova_region_nr; i++) {
|
|
|
|
resv = data->plat_data->iova_region + i;
|
|
|
|
|
|
|
|
/* Only reserve when the region is inside the current domain */
|
|
|
|
if (resv->iova_base <= curdom->iova_base ||
|
|
|
|
resv->iova_base + resv->size >= curdom->iova_base + curdom->size)
|
|
|
|
continue;
|
|
|
|
|
|
|
|
region = iommu_alloc_resv_region(resv->iova_base, resv->size,
|
|
|
|
prot, IOMMU_RESV_RESERVED);
|
|
|
|
if (!region)
|
|
|
|
return;
|
|
|
|
|
|
|
|
list_add_tail(®ion->list, head);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-10-18 11:13:38 +00:00
|
|
|
static const struct iommu_ops mtk_iommu_ops = {
|
2016-02-22 17:20:50 +00:00
|
|
|
.domain_alloc = mtk_iommu_domain_alloc,
|
|
|
|
.domain_free = mtk_iommu_domain_free,
|
|
|
|
.attach_dev = mtk_iommu_attach_device,
|
|
|
|
.detach_dev = mtk_iommu_detach_device,
|
|
|
|
.map = mtk_iommu_map,
|
|
|
|
.unmap = mtk_iommu_unmap,
|
2019-07-02 15:44:06 +00:00
|
|
|
.flush_iotlb_all = mtk_iommu_flush_iotlb_all,
|
2017-09-28 14:55:02 +00:00
|
|
|
.iotlb_sync = mtk_iommu_iotlb_sync,
|
2021-01-07 12:29:05 +00:00
|
|
|
.iotlb_sync_map = mtk_iommu_sync_map,
|
2016-02-22 17:20:50 +00:00
|
|
|
.iova_to_phys = mtk_iommu_iova_to_phys,
|
2020-04-29 13:37:00 +00:00
|
|
|
.probe_device = mtk_iommu_probe_device,
|
|
|
|
.release_device = mtk_iommu_release_device,
|
2016-02-22 17:20:50 +00:00
|
|
|
.device_group = mtk_iommu_device_group,
|
|
|
|
.of_xlate = mtk_iommu_of_xlate,
|
2021-01-11 11:19:10 +00:00
|
|
|
.get_resv_regions = mtk_iommu_get_resv_regions,
|
|
|
|
.put_resv_regions = generic_iommu_put_resv_regions,
|
2016-02-22 17:20:50 +00:00
|
|
|
.pgsize_bitmap = SZ_4K | SZ_64K | SZ_1M | SZ_16M,
|
2021-03-26 03:23:37 +00:00
|
|
|
.owner = THIS_MODULE,
|
2016-02-22 17:20:50 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
static int mtk_iommu_hw_init(const struct mtk_iommu_data *data)
|
|
|
|
{
|
|
|
|
u32 regval;
|
|
|
|
|
2020-07-03 04:41:26 +00:00
|
|
|
if (data->plat_data->m4u_plat == M4U_MT8173) {
|
2019-08-24 03:01:58 +00:00
|
|
|
regval = F_MMU_PREFETCH_RT_REPLACE_MOD |
|
|
|
|
F_MMU_TF_PROT_TO_PROGRAM_ADDR_MT8173;
|
2020-07-03 04:41:26 +00:00
|
|
|
} else {
|
|
|
|
regval = readl_relaxed(data->base + REG_MMU_CTRL_REG);
|
|
|
|
regval |= F_MMU_TF_PROT_TO_PROGRAM_ADDR;
|
|
|
|
}
|
2016-02-22 17:20:50 +00:00
|
|
|
writel_relaxed(regval, data->base + REG_MMU_CTRL_REG);
|
|
|
|
|
|
|
|
regval = F_L2_MULIT_HIT_EN |
|
|
|
|
F_TABLE_WALK_FAULT_INT_EN |
|
|
|
|
F_PREETCH_FIFO_OVERFLOW_INT_EN |
|
|
|
|
F_MISS_FIFO_OVERFLOW_INT_EN |
|
|
|
|
F_PREFETCH_FIFO_ERR_INT_EN |
|
|
|
|
F_MISS_FIFO_ERR_INT_EN;
|
|
|
|
writel_relaxed(regval, data->base + REG_MMU_INT_CONTROL0);
|
|
|
|
|
|
|
|
regval = F_INT_TRANSLATION_FAULT |
|
|
|
|
F_INT_MAIN_MULTI_HIT_FAULT |
|
|
|
|
F_INT_INVALID_PA_FAULT |
|
|
|
|
F_INT_ENTRY_REPLACEMENT_FAULT |
|
|
|
|
F_INT_TLB_MISS_FAULT |
|
|
|
|
F_INT_MISS_TRANSACTION_FIFO_FAULT |
|
|
|
|
F_INT_PRETETCH_TRANSATION_FIFO_FAULT;
|
|
|
|
writel_relaxed(regval, data->base + REG_MMU_INT_MAIN_CONTROL);
|
|
|
|
|
2020-09-07 10:16:48 +00:00
|
|
|
if (MTK_IOMMU_HAS_FLAG(data->plat_data, HAS_LEGACY_IVRP_PADDR))
|
2018-03-18 01:52:54 +00:00
|
|
|
regval = (data->protect_base >> 1) | (data->enable_4GB << 31);
|
|
|
|
else
|
|
|
|
regval = lower_32_bits(data->protect_base) |
|
|
|
|
upper_32_bits(data->protect_base);
|
|
|
|
writel_relaxed(regval, data->base + REG_MMU_IVRP_PADDR);
|
|
|
|
|
2020-07-03 04:41:20 +00:00
|
|
|
if (data->enable_4GB &&
|
|
|
|
MTK_IOMMU_HAS_FLAG(data->plat_data, HAS_VLD_PA_RNG)) {
|
2017-08-21 11:00:20 +00:00
|
|
|
/*
|
|
|
|
* If 4GB mode is enabled, the validate PA range is from
|
|
|
|
* 0x1_0000_0000 to 0x1_ffff_ffff. here record bit[32:30].
|
|
|
|
*/
|
|
|
|
regval = F_MMU_VLD_PA_RNG(7, 4);
|
|
|
|
writel_relaxed(regval, data->base + REG_MMU_VLD_PA_RNG);
|
|
|
|
}
|
2016-02-22 17:20:50 +00:00
|
|
|
writel_relaxed(0, data->base + REG_MMU_DCM_DIS);
|
2020-07-03 04:41:24 +00:00
|
|
|
if (MTK_IOMMU_HAS_FLAG(data->plat_data, WR_THROT_EN)) {
|
|
|
|
/* write command throttling mode */
|
|
|
|
regval = readl_relaxed(data->base + REG_MMU_WR_LEN_CTRL);
|
|
|
|
regval &= ~F_MMU_WR_THROT_DIS_MASK;
|
|
|
|
writel_relaxed(regval, data->base + REG_MMU_WR_LEN_CTRL);
|
|
|
|
}
|
2017-08-21 11:00:16 +00:00
|
|
|
|
2020-07-03 04:41:20 +00:00
|
|
|
if (MTK_IOMMU_HAS_FLAG(data->plat_data, RESET_AXI)) {
|
2020-07-03 04:41:19 +00:00
|
|
|
/* The register is called STANDARD_AXI_MODE in this case */
|
2020-07-03 04:41:21 +00:00
|
|
|
regval = 0;
|
|
|
|
} else {
|
|
|
|
regval = readl_relaxed(data->base + REG_MMU_MISC_CTRL);
|
|
|
|
regval &= ~F_MMU_STANDARD_AXI_MODE_MASK;
|
|
|
|
if (MTK_IOMMU_HAS_FLAG(data->plat_data, OUT_ORDER_WR_EN))
|
|
|
|
regval &= ~F_MMU_IN_ORDER_WR_EN_MASK;
|
2020-07-03 04:41:19 +00:00
|
|
|
}
|
2020-07-03 04:41:21 +00:00
|
|
|
writel_relaxed(regval, data->base + REG_MMU_MISC_CTRL);
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
if (devm_request_irq(data->dev, data->irq, mtk_iommu_isr, 0,
|
|
|
|
dev_name(data->dev), (void *)data)) {
|
|
|
|
writel_relaxed(0, data->base + REG_MMU_PT_BASE_ADDR);
|
|
|
|
dev_err(data->dev, "Failed @ IRQ-%d Request\n", data->irq);
|
|
|
|
return -ENODEV;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static const struct component_master_ops mtk_iommu_com_ops = {
|
|
|
|
.bind = mtk_iommu_bind,
|
|
|
|
.unbind = mtk_iommu_unbind,
|
|
|
|
};
|
|
|
|
|
|
|
|
static int mtk_iommu_probe(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
struct mtk_iommu_data *data;
|
|
|
|
struct device *dev = &pdev->dev;
|
2021-01-11 11:18:59 +00:00
|
|
|
struct device_node *larbnode, *smicomm_node;
|
|
|
|
struct platform_device *plarbdev;
|
|
|
|
struct device_link *link;
|
2016-02-22 17:20:50 +00:00
|
|
|
struct resource *res;
|
2017-02-03 11:57:32 +00:00
|
|
|
resource_size_t ioaddr;
|
2016-02-22 17:20:50 +00:00
|
|
|
struct component_match *match = NULL;
|
2020-09-04 10:40:38 +00:00
|
|
|
struct regmap *infracfg;
|
2016-02-22 17:20:50 +00:00
|
|
|
void *protect;
|
2016-03-01 09:36:23 +00:00
|
|
|
int i, larb_nr, ret;
|
2020-09-04 10:40:38 +00:00
|
|
|
u32 val;
|
|
|
|
char *p;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
data = devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
|
|
|
|
if (!data)
|
|
|
|
return -ENOMEM;
|
|
|
|
data->dev = dev;
|
2019-08-24 03:01:47 +00:00
|
|
|
data->plat_data = of_device_get_match_data(dev);
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
/* Protect memory. HW will access here while translation fault.*/
|
|
|
|
protect = devm_kzalloc(dev, MTK_PROTECT_PA_ALIGN * 2, GFP_KERNEL);
|
|
|
|
if (!protect)
|
|
|
|
return -ENOMEM;
|
|
|
|
data->protect_base = ALIGN(virt_to_phys(protect), MTK_PROTECT_PA_ALIGN);
|
|
|
|
|
2020-09-04 10:40:38 +00:00
|
|
|
if (MTK_IOMMU_HAS_FLAG(data->plat_data, HAS_4GB_MODE)) {
|
|
|
|
switch (data->plat_data->m4u_plat) {
|
|
|
|
case M4U_MT2712:
|
|
|
|
p = "mediatek,mt2712-infracfg";
|
|
|
|
break;
|
|
|
|
case M4U_MT8173:
|
|
|
|
p = "mediatek,mt8173-infracfg";
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
p = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
infracfg = syscon_regmap_lookup_by_compatible(p);
|
|
|
|
|
|
|
|
if (IS_ERR(infracfg))
|
|
|
|
return PTR_ERR(infracfg);
|
|
|
|
|
|
|
|
ret = regmap_read(infracfg, REG_INFRA_MISC, &val);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
data->enable_4GB = !!(val & F_DDR_4GB_SUPPORT_EN);
|
|
|
|
}
|
2016-03-13 22:01:11 +00:00
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
|
|
|
|
data->base = devm_ioremap_resource(dev, res);
|
|
|
|
if (IS_ERR(data->base))
|
|
|
|
return PTR_ERR(data->base);
|
2017-02-03 11:57:32 +00:00
|
|
|
ioaddr = res->start;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
data->irq = platform_get_irq(pdev, 0);
|
|
|
|
if (data->irq < 0)
|
|
|
|
return data->irq;
|
|
|
|
|
2020-07-03 04:41:20 +00:00
|
|
|
if (MTK_IOMMU_HAS_FLAG(data->plat_data, HAS_BCLK)) {
|
2019-08-24 03:01:56 +00:00
|
|
|
data->bclk = devm_clk_get(dev, "bclk");
|
|
|
|
if (IS_ERR(data->bclk))
|
|
|
|
return PTR_ERR(data->bclk);
|
|
|
|
}
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
larb_nr = of_count_phandle_with_args(dev->of_node,
|
|
|
|
"mediatek,larbs", NULL);
|
|
|
|
if (larb_nr < 0)
|
|
|
|
return larb_nr;
|
|
|
|
|
|
|
|
for (i = 0; i < larb_nr; i++) {
|
2017-08-21 11:00:16 +00:00
|
|
|
u32 id;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
|
|
|
larbnode = of_parse_phandle(dev->of_node, "mediatek,larbs", i);
|
|
|
|
if (!larbnode)
|
|
|
|
return -EINVAL;
|
|
|
|
|
2019-04-17 02:41:19 +00:00
|
|
|
if (!of_device_is_available(larbnode)) {
|
|
|
|
of_node_put(larbnode);
|
2016-02-22 17:20:50 +00:00
|
|
|
continue;
|
2019-04-17 02:41:19 +00:00
|
|
|
}
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2017-08-21 11:00:16 +00:00
|
|
|
ret = of_property_read_u32(larbnode, "mediatek,larb-id", &id);
|
|
|
|
if (ret)/* The id is consecutive if there is no this property */
|
|
|
|
id = i;
|
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
plarbdev = of_find_device_by_node(larbnode);
|
2019-04-17 02:41:19 +00:00
|
|
|
if (!plarbdev) {
|
|
|
|
of_node_put(larbnode);
|
2022-01-17 07:05:00 +00:00
|
|
|
return -ENODEV;
|
2019-04-17 02:41:19 +00:00
|
|
|
}
|
2019-08-24 03:02:08 +00:00
|
|
|
data->larb_imu[id].dev = &plarbdev->dev;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2016-10-19 10:30:34 +00:00
|
|
|
component_match_add_release(dev, &match, release_of,
|
|
|
|
compare_of, larbnode);
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
2021-01-11 11:18:59 +00:00
|
|
|
/* Get smi-common dev from the last larb. */
|
|
|
|
smicomm_node = of_parse_phandle(larbnode, "mediatek,smi", 0);
|
|
|
|
if (!smicomm_node)
|
|
|
|
return -EINVAL;
|
|
|
|
|
|
|
|
plarbdev = of_find_device_by_node(smicomm_node);
|
|
|
|
of_node_put(smicomm_node);
|
|
|
|
data->smicomm_dev = &plarbdev->dev;
|
|
|
|
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
pm_runtime_enable(dev);
|
|
|
|
|
2021-01-11 11:18:59 +00:00
|
|
|
link = device_link_add(data->smicomm_dev, dev,
|
|
|
|
DL_FLAG_STATELESS | DL_FLAG_PM_RUNTIME);
|
|
|
|
if (!link) {
|
2021-02-05 12:46:17 +00:00
|
|
|
dev_err(dev, "Unable to link %s.\n", dev_name(data->smicomm_dev));
|
|
|
|
ret = -EINVAL;
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
goto out_runtime_disable;
|
2021-01-11 11:18:59 +00:00
|
|
|
}
|
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
platform_set_drvdata(pdev, data);
|
2022-05-03 07:13:58 +00:00
|
|
|
mutex_init(&data->mutex);
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2017-02-03 11:57:32 +00:00
|
|
|
ret = iommu_device_sysfs_add(&data->iommu, dev, NULL,
|
|
|
|
"mtk-iommu.%pa", &ioaddr);
|
|
|
|
if (ret)
|
2021-01-11 11:18:59 +00:00
|
|
|
goto out_link_remove;
|
2017-02-03 11:57:32 +00:00
|
|
|
|
2021-04-01 13:56:26 +00:00
|
|
|
ret = iommu_device_register(&data->iommu, &mtk_iommu_ops, dev);
|
2017-02-03 11:57:32 +00:00
|
|
|
if (ret)
|
2021-01-11 11:18:58 +00:00
|
|
|
goto out_sysfs_remove;
|
2017-02-03 11:57:32 +00:00
|
|
|
|
2019-11-04 07:01:03 +00:00
|
|
|
spin_lock_init(&data->tlb_lock);
|
2017-08-21 11:00:17 +00:00
|
|
|
list_add_tail(&data->list, &m4ulist);
|
|
|
|
|
2021-01-11 11:18:58 +00:00
|
|
|
if (!iommu_present(&platform_bus_type)) {
|
|
|
|
ret = bus_set_iommu(&platform_bus_type, &mtk_iommu_ops);
|
|
|
|
if (ret)
|
|
|
|
goto out_list_del;
|
|
|
|
}
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2021-01-11 11:18:58 +00:00
|
|
|
ret = component_master_add_with_match(dev, &mtk_iommu_com_ops, match);
|
|
|
|
if (ret)
|
|
|
|
goto out_bus_set_null;
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
out_bus_set_null:
|
|
|
|
bus_set_iommu(&platform_bus_type, NULL);
|
|
|
|
out_list_del:
|
|
|
|
list_del(&data->list);
|
|
|
|
iommu_device_unregister(&data->iommu);
|
|
|
|
out_sysfs_remove:
|
|
|
|
iommu_device_sysfs_remove(&data->iommu);
|
2021-01-11 11:18:59 +00:00
|
|
|
out_link_remove:
|
|
|
|
device_link_remove(data->smicomm_dev, dev);
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
out_runtime_disable:
|
|
|
|
pm_runtime_disable(dev);
|
2021-01-11 11:18:58 +00:00
|
|
|
return ret;
|
2016-02-22 17:20:50 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
static int mtk_iommu_remove(struct platform_device *pdev)
|
|
|
|
{
|
|
|
|
struct mtk_iommu_data *data = platform_get_drvdata(pdev);
|
|
|
|
|
2017-02-03 11:57:32 +00:00
|
|
|
iommu_device_sysfs_remove(&data->iommu);
|
|
|
|
iommu_device_unregister(&data->iommu);
|
|
|
|
|
2022-05-03 07:13:56 +00:00
|
|
|
list_del(&data->list);
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2021-01-11 11:18:59 +00:00
|
|
|
device_link_remove(data->smicomm_dev, &pdev->dev);
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
pm_runtime_disable(&pdev->dev);
|
2016-02-22 17:20:50 +00:00
|
|
|
devm_free_irq(&pdev->dev, data->irq, data);
|
|
|
|
component_master_del(&pdev->dev, &mtk_iommu_com_ops);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2021-01-11 11:19:00 +00:00
|
|
|
static int __maybe_unused mtk_iommu_runtime_suspend(struct device *dev)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
|
|
|
struct mtk_iommu_data *data = dev_get_drvdata(dev);
|
|
|
|
struct mtk_iommu_suspend_reg *reg = &data->reg;
|
|
|
|
void __iomem *base = data->base;
|
|
|
|
|
2020-07-03 04:41:24 +00:00
|
|
|
reg->wr_len_ctrl = readl_relaxed(base + REG_MMU_WR_LEN_CTRL);
|
2020-07-03 04:41:19 +00:00
|
|
|
reg->misc_ctrl = readl_relaxed(base + REG_MMU_MISC_CTRL);
|
2016-02-22 17:20:50 +00:00
|
|
|
reg->dcm_dis = readl_relaxed(base + REG_MMU_DCM_DIS);
|
|
|
|
reg->ctrl_reg = readl_relaxed(base + REG_MMU_CTRL_REG);
|
|
|
|
reg->int_control0 = readl_relaxed(base + REG_MMU_INT_CONTROL0);
|
|
|
|
reg->int_main_control = readl_relaxed(base + REG_MMU_INT_MAIN_CONTROL);
|
2018-03-18 01:52:54 +00:00
|
|
|
reg->ivrp_paddr = readl_relaxed(base + REG_MMU_IVRP_PADDR);
|
2019-08-24 03:02:06 +00:00
|
|
|
reg->vld_pa_rng = readl_relaxed(base + REG_MMU_VLD_PA_RNG);
|
2017-08-21 11:00:19 +00:00
|
|
|
clk_disable_unprepare(data->bclk);
|
2016-02-22 17:20:50 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2021-01-11 11:19:00 +00:00
|
|
|
static int __maybe_unused mtk_iommu_runtime_resume(struct device *dev)
|
2016-02-22 17:20:50 +00:00
|
|
|
{
|
|
|
|
struct mtk_iommu_data *data = dev_get_drvdata(dev);
|
|
|
|
struct mtk_iommu_suspend_reg *reg = &data->reg;
|
2019-08-24 03:02:02 +00:00
|
|
|
struct mtk_iommu_domain *m4u_dom = data->m4u_dom;
|
2016-02-22 17:20:50 +00:00
|
|
|
void __iomem *base = data->base;
|
2017-08-21 11:00:19 +00:00
|
|
|
int ret;
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2017-08-21 11:00:19 +00:00
|
|
|
ret = clk_prepare_enable(data->bclk);
|
|
|
|
if (ret) {
|
|
|
|
dev_err(data->dev, "Failed to enable clk(%d) in resume\n", ret);
|
|
|
|
return ret;
|
|
|
|
}
|
2021-04-16 10:54:49 +00:00
|
|
|
|
|
|
|
/*
|
|
|
|
* Uppon first resume, only enable the clk and return, since the values of the
|
|
|
|
* registers are not yet set.
|
|
|
|
*/
|
|
|
|
if (!m4u_dom)
|
|
|
|
return 0;
|
|
|
|
|
2020-07-03 04:41:24 +00:00
|
|
|
writel_relaxed(reg->wr_len_ctrl, base + REG_MMU_WR_LEN_CTRL);
|
2020-07-03 04:41:19 +00:00
|
|
|
writel_relaxed(reg->misc_ctrl, base + REG_MMU_MISC_CTRL);
|
2016-02-22 17:20:50 +00:00
|
|
|
writel_relaxed(reg->dcm_dis, base + REG_MMU_DCM_DIS);
|
|
|
|
writel_relaxed(reg->ctrl_reg, base + REG_MMU_CTRL_REG);
|
|
|
|
writel_relaxed(reg->int_control0, base + REG_MMU_INT_CONTROL0);
|
|
|
|
writel_relaxed(reg->int_main_control, base + REG_MMU_INT_MAIN_CONTROL);
|
2018-03-18 01:52:54 +00:00
|
|
|
writel_relaxed(reg->ivrp_paddr, base + REG_MMU_IVRP_PADDR);
|
2019-08-24 03:02:06 +00:00
|
|
|
writel_relaxed(reg->vld_pa_rng, base + REG_MMU_VLD_PA_RNG);
|
iommu/mediatek: Add power-domain operation
In the previous SoC, the M4U HW is in the EMI power domain which is
always on. the latest M4U is in the display power domain which may be
turned on/off, thus we have to add pm_runtime interface for it.
When the engine work, the engine always enable the power and clocks for
smi-larb/smi-common, then the M4U's power will always be powered on
automatically via the device link with smi-common.
Note: we don't enable the M4U power in iommu_map/unmap for tlb flush.
If its power already is on, of course it is ok. if the power is off,
the main tlb will be reset while M4U power on, thus the tlb flush while
m4u power off is unnecessary, just skip it.
Therefore, we increase the ref_count for pm when pm status is ACTIVE,
otherwise, skip it. Meanwhile, the tlb_flush_range is called so often,
thus, update pm ref_count while the SoC has power-domain to avoid touch the
dev->power.lock. and the tlb_flush_all only is called when boot, so no
need check if the SoC has power-domain to keep code clean.
There will be one case that pm runctime status is not expected when tlb
flush. After boot, the display may call dma_alloc_attrs before it call
pm_runtime_get(disp-dev), then the m4u's pm status is not active inside
the dma_alloc_attrs. Since it only happens after boot, the tlb is clean
at that time, I also think this is ok.
Signed-off-by: Yong Wu <yong.wu@mediatek.com>
Reviewed-by: Tomasz Figa <tfiga@chromium.org>
Link: https://lore.kernel.org/r/20210111111914.22211-21-yong.wu@mediatek.com
Signed-off-by: Will Deacon <will@kernel.org>
2021-01-11 11:19:01 +00:00
|
|
|
writel(m4u_dom->cfg.arm_v7s_cfg.ttbr & MMU_PT_ADDR_MASK, base + REG_MMU_PT_BASE_ADDR);
|
2016-02-22 17:20:50 +00:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2017-08-21 11:00:16 +00:00
|
|
|
static const struct dev_pm_ops mtk_iommu_pm_ops = {
|
2021-01-11 11:19:00 +00:00
|
|
|
SET_RUNTIME_PM_OPS(mtk_iommu_runtime_suspend, mtk_iommu_runtime_resume, NULL)
|
|
|
|
SET_LATE_SYSTEM_SLEEP_PM_OPS(pm_runtime_force_suspend,
|
|
|
|
pm_runtime_force_resume)
|
2016-02-22 17:20:50 +00:00
|
|
|
};
|
|
|
|
|
2019-08-24 03:01:47 +00:00
|
|
|
static const struct mtk_iommu_plat_data mt2712_data = {
|
|
|
|
.m4u_plat = M4U_MT2712,
|
2020-07-03 04:41:20 +00:00
|
|
|
.flags = HAS_4GB_MODE | HAS_BCLK | HAS_VLD_PA_RNG,
|
2020-07-03 04:41:22 +00:00
|
|
|
.inv_sel_reg = REG_MMU_INV_SEL_GEN1,
|
2021-01-11 11:19:07 +00:00
|
|
|
.iova_region = single_domain,
|
|
|
|
.iova_region_nr = ARRAY_SIZE(single_domain),
|
2020-07-03 04:41:23 +00:00
|
|
|
.larbid_remap = {{0}, {1}, {2}, {3}, {4}, {5}, {6}, {7}},
|
2019-08-24 03:01:47 +00:00
|
|
|
};
|
|
|
|
|
2020-07-03 04:41:27 +00:00
|
|
|
static const struct mtk_iommu_plat_data mt6779_data = {
|
|
|
|
.m4u_plat = M4U_MT6779,
|
|
|
|
.flags = HAS_SUB_COMM | OUT_ORDER_WR_EN | WR_THROT_EN,
|
|
|
|
.inv_sel_reg = REG_MMU_INV_SEL_GEN2,
|
2021-01-11 11:19:07 +00:00
|
|
|
.iova_region = single_domain,
|
|
|
|
.iova_region_nr = ARRAY_SIZE(single_domain),
|
2020-07-03 04:41:27 +00:00
|
|
|
.larbid_remap = {{0}, {1}, {2}, {3}, {5}, {7, 8}, {10}, {9}},
|
2019-08-24 03:01:47 +00:00
|
|
|
};
|
|
|
|
|
2020-09-07 10:16:49 +00:00
|
|
|
static const struct mtk_iommu_plat_data mt8167_data = {
|
|
|
|
.m4u_plat = M4U_MT8167,
|
|
|
|
.flags = RESET_AXI | HAS_LEGACY_IVRP_PADDR,
|
|
|
|
.inv_sel_reg = REG_MMU_INV_SEL_GEN1,
|
2021-01-11 11:19:07 +00:00
|
|
|
.iova_region = single_domain,
|
|
|
|
.iova_region_nr = ARRAY_SIZE(single_domain),
|
2020-09-07 10:16:49 +00:00
|
|
|
.larbid_remap = {{0}, {1}, {2}}, /* Linear mapping. */
|
|
|
|
};
|
|
|
|
|
2019-08-24 03:01:47 +00:00
|
|
|
static const struct mtk_iommu_plat_data mt8173_data = {
|
|
|
|
.m4u_plat = M4U_MT8173,
|
2020-09-07 10:16:48 +00:00
|
|
|
.flags = HAS_4GB_MODE | HAS_BCLK | RESET_AXI |
|
|
|
|
HAS_LEGACY_IVRP_PADDR,
|
2020-07-03 04:41:22 +00:00
|
|
|
.inv_sel_reg = REG_MMU_INV_SEL_GEN1,
|
2021-01-11 11:19:07 +00:00
|
|
|
.iova_region = single_domain,
|
|
|
|
.iova_region_nr = ARRAY_SIZE(single_domain),
|
2020-07-03 04:41:23 +00:00
|
|
|
.larbid_remap = {{0}, {1}, {2}, {3}, {4}, {5}}, /* Linear mapping. */
|
2019-08-24 03:01:47 +00:00
|
|
|
};
|
|
|
|
|
2019-08-24 03:02:02 +00:00
|
|
|
static const struct mtk_iommu_plat_data mt8183_data = {
|
|
|
|
.m4u_plat = M4U_MT8183,
|
2020-07-03 04:41:20 +00:00
|
|
|
.flags = RESET_AXI,
|
2020-07-03 04:41:22 +00:00
|
|
|
.inv_sel_reg = REG_MMU_INV_SEL_GEN1,
|
2021-01-11 11:19:07 +00:00
|
|
|
.iova_region = single_domain,
|
|
|
|
.iova_region_nr = ARRAY_SIZE(single_domain),
|
2020-07-03 04:41:23 +00:00
|
|
|
.larbid_remap = {{0}, {4}, {5}, {6}, {7}, {2}, {3}, {1}},
|
2019-08-24 03:02:02 +00:00
|
|
|
};
|
|
|
|
|
2021-01-11 11:19:13 +00:00
|
|
|
static const struct mtk_iommu_plat_data mt8192_data = {
|
|
|
|
.m4u_plat = M4U_MT8192,
|
|
|
|
.flags = HAS_BCLK | HAS_SUB_COMM | OUT_ORDER_WR_EN |
|
|
|
|
WR_THROT_EN | IOVA_34_EN,
|
|
|
|
.inv_sel_reg = REG_MMU_INV_SEL_GEN2,
|
|
|
|
.iova_region = mt8192_multi_dom,
|
|
|
|
.iova_region_nr = ARRAY_SIZE(mt8192_multi_dom),
|
|
|
|
.larbid_remap = {{0}, {1}, {4, 5}, {7}, {2}, {9, 11, 19, 20},
|
|
|
|
{0, 14, 16}, {0, 13, 18, 17}},
|
|
|
|
};
|
|
|
|
|
2016-02-22 17:20:50 +00:00
|
|
|
static const struct of_device_id mtk_iommu_of_ids[] = {
|
2019-08-24 03:01:47 +00:00
|
|
|
{ .compatible = "mediatek,mt2712-m4u", .data = &mt2712_data},
|
2020-07-03 04:41:27 +00:00
|
|
|
{ .compatible = "mediatek,mt6779-m4u", .data = &mt6779_data},
|
2020-09-07 10:16:49 +00:00
|
|
|
{ .compatible = "mediatek,mt8167-m4u", .data = &mt8167_data},
|
2019-08-24 03:01:47 +00:00
|
|
|
{ .compatible = "mediatek,mt8173-m4u", .data = &mt8173_data},
|
2019-08-24 03:02:02 +00:00
|
|
|
{ .compatible = "mediatek,mt8183-m4u", .data = &mt8183_data},
|
2021-01-11 11:19:13 +00:00
|
|
|
{ .compatible = "mediatek,mt8192-m4u", .data = &mt8192_data},
|
2016-02-22 17:20:50 +00:00
|
|
|
{}
|
|
|
|
};
|
|
|
|
|
|
|
|
static struct platform_driver mtk_iommu_driver = {
|
|
|
|
.probe = mtk_iommu_probe,
|
|
|
|
.remove = mtk_iommu_remove,
|
|
|
|
.driver = {
|
|
|
|
.name = "mtk-iommu",
|
2020-07-27 18:18:42 +00:00
|
|
|
.of_match_table = mtk_iommu_of_ids,
|
2016-02-22 17:20:50 +00:00
|
|
|
.pm = &mtk_iommu_pm_ops,
|
|
|
|
}
|
|
|
|
};
|
2021-03-26 03:23:37 +00:00
|
|
|
module_platform_driver(mtk_iommu_driver);
|
2016-02-22 17:20:50 +00:00
|
|
|
|
2021-03-26 03:23:37 +00:00
|
|
|
MODULE_DESCRIPTION("IOMMU API for MediaTek M4U implementations");
|
|
|
|
MODULE_LICENSE("GPL v2");
|