iommu/ipmmu-vmsa: r8a7795 support V2
v2 cover iommu/ipmmu-vmsa: r8a7795 support V2
iommu/ipmmu-vmsa: r8a7795 support V2
[PATCH v2 01/11] iommu/ipmmu-vmsa: Introduce features, break out alias [PATCH v2 02/11] iommu/ipmmu-vmsa: Add optional root device feature [PATCH v2 03/11] iommu/ipmmu-vmsa: Enable multi context support [PATCH v2 04/11] iommu/ipmmu-vmsa: Reuse iommu groups
[PATCH v2 05/11] iommu/ipmmu-vmsa: Make use of IOMMU_OF_DECLARE() [PATCH v2 06/11] iommu/ipmmu-vmsa: Teach xlate() to skip disabled iommus [PATCH v2 07/11] iommu/ipmmu-vmsa: IPMMU device is 64-bit bus master [PATCH v2 08/11] iommu/ipmmu-vmsa: Write IMCTR twice
[PATCH v2 09/11] iommu/ipmmu-vmsa: Make IMBUSCTR setup optional [PATCH v2 10/11] iommu/ipmmu-vmsa: Allow two bit SL0
[PATCH v2 11/11] iommu/ipmmu-vmsa: Hook up r8a7795 DT matching code
This series contains updated r8a7795 support for the IPMMU driver compared to the earlier series posted as:
[PATCH 00/10] iommu/ipmmu-vmsa: Initial r8a7795 support
The DT binding for r8a7795 has been accepted for upstream merge and this series implements support following such format:
d4e42e7 iommu/ipmmu-vmsa: Add r8a7795 DT binding
The r8a7795 IPMMU is almost register compatible with earlier devices like r8a7790-r8a7794, however some bitfields have been shifted slightly. On a grander scale topology has been added and interrupts have been reworked. So now there are several "cache" IPMMU units without interrupt that somehow communicate with IPMMU-MM that is the only instance that supports interrupts. The code refers to IPMMU-MM as a "root" device and the other ones as leaf nodes.
To make this more interesting the IPMMU driver needs to be shared between 32-bit ARM for r8a7790-r8a7794 and 64-bit ARM for r8a7795. In practice this means that two separate implementations are needed inside the driver to attach to the rather different architecture specific code.
CONFIG_IOMMU_DMA=y is needed on 64-bit ARM while on 32-bit ARM the arch specific dma-mapping code is hooked up rather directly. During init 64-bit ARM IPMMU support is relying on IOMMU_OF_DECLARE().
This version of the code is known to build on 32-bit and 64-bit ARM.
Compared to V1 the patches have been reordered and multi context and iommu group code has been reworked. Now devices are grouped together based on the IPMMU they are connected to. For detail please see the change log in each individual patch.
---
Developed on top of next-20160602 and:
[PATCH v3 00/06] iommu/ipmmu-vmsa: IPMMU multi-arch update V3
drivers/iommu/ipmmu-vmsa.c | 318 +++++++++++++++++++++++++++++++++++++------- 1 file changed, 269 insertions(+), 49 deletions(-)
PATCH v2 1/11 iommu/ipmmu-vmsa: Introduce features, break out alias
From: Magnus Damm <[email protected]>
Introduce struct ipmmu_features to track various hardware and software implementation changes inside the driver for different kinds of IPMMU hardware. Add use_ns_alias_offset as a first example of a feature to control if the secure register bank offset should be used or not.
---
Changes since V1:
- Moved patch to front of the series
drivers/iommu/ipmmu-vmsa.c | 35 ++++++++++++++++++++++++++++------- 1 file changed, 28 insertions(+), 7 deletions(-)
drivers/iommu/ipmmu-vmsa.c +28 -7
@@ -32,11 +32,15 @@#define IPMMU_CTX_MAX 1 +struct ipmmu_features { +bool use_ns_alias_offset; +}; +struct ipmmu_vmsa_device {struct device *dev;void __iomem *base;struct list_head list; - +const struct ipmmu_features *features;unsigned int num_utlbs;spinlock_t lock;/* Protects ctx and domains[] */ DECLARE_BITMAP(ctx, IPMMU_CTX_MAX);
@@ -929,13 +933,33 @@ static void ipmmu_device_reset(struct ipipmmu_write (mmu, i *IM_CTX_SIZE +IMCTR ,0 ); } +static const struct ipmmu_features ipmmu_features_default = { + .use_ns_alias_offset = true, +}; + +static const struct of_device_id ipmmu_of_ids[] = { + { + .compatible ="renesas,ipmmu-vmsa" , + .data = &ipmmu_features_default, + }, { +/* Terminator */ + }, +}; + +MODULE_DEVICE_TABLE (of, ipmmu_of_ids); +static int ipmmu_probe (struct platform_device *pdev) {struct ipmmu_vmsa_device *mmu; +const struct of_device_id *match;struct resource *res;int irq;int ret; + match =of_match_node (ipmmu_of_ids, pdev->dev.of_node); +if (!match) +return -EINVAL ; + mmu =devm_kzalloc (&pdev->dev,sizeof (*mmu),GFP_KERNEL );if (!mmu) {dev_err (&pdev->dev,"cannot allocate device data\n" );
@@ -946,6 +970,7 @@ static int ipmmu_probe(struct platform_d mmu->num_utlbs =32 ;spin_lock_init (&mmu->lock);bitmap_zero (mmu->ctx,IPMMU_CTX_MAX ); + mmu->features = match->data;/* Map I/O memory and request IRQ. */ res =platform_get_resource (pdev,IORESOURCE_MEM ,0 );
@@ -965,7 +990,8 @@ static int ipmmu_probe(struct platform_d* Offset the registers base unconditionally to point to the non-secure * alias space for now. */ - mmu->base +=IM_NS_ALIAS_OFFSET ; +if (mmu->features->use_ns_alias_offset) + mmu->base +=IM_NS_ALIAS_OFFSET ; irq =platform_get_irq (pdev,0 );if (irq <0 ) {
@@ -1014,11 +1040,6 @@ static int ipmmu_remove(struct platform_return 0 ; } -static const struct of_device_id ipmmu_of_ids[] = { - { .compatible ="renesas,ipmmu-vmsa" , }, - { } -}; -static struct platform_driver ipmmu_driver = { .driver = { .name ="ipmmu-vmsa" ,
PATCH v2 2/11 iommu/ipmmu-vmsa: Add optional root device feature
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
Add root device handling to the IPMMU driver by allowing certain DT compat strings to enable has_cache_leaf_nodes that in turn will support both root devices with interrupts and leaf devices that face the actual IPMMU consumer devices.
---
Changes since V1:
- Moved patch to earlier in the series
- Updated code to work with recent changes in:
[PATCH v3 00/06] iommu/ipmmu-vmsa: IPMMU multi-arch update V3
drivers/iommu/ipmmu-vmsa.c | 87 +++++++++++++++++++++++++++++++++++--------- 1 file changed, 70 insertions(+), 17 deletions(-)
drivers/iommu/ipmmu-vmsa.c +70 -17
@@ -34,6 +34,7 @@struct ipmmu_features {bool use_ns_alias_offset; +bool has_cache_leaf_nodes; };struct ipmmu_vmsa_device {
@@ -41,6 +42,7 @@ struct ipmmu_vmsa_device {void __iomem *base;struct list_head list;const struct ipmmu_features *features; +bool is_leaf;unsigned int num_utlbs;spinlock_t lock;/* Protects ctx and domains[] */ DECLARE_BITMAP (ctx,IPMMU_CTX_MAX );
@@ -51,6 +53,7 @@ struct ipmmu_vmsa_device {struct ipmmu_vmsa_domain {struct ipmmu_vmsa_device *mmu; +struct ipmmu_vmsa_device *root;struct iommu_domain io_domain;struct io_pgtable_cfg cfg;
@@ -195,6 +198,36 @@ static struct ipmmu_vmsa_domain *to_vmsa#define IMUASID_ASID0_SHIFT 0/* ----------------------------------------------------------------------------- +* Root device handling +*/ + +static bool ipmmu_is_root (struct ipmmu_vmsa_device *mmu) +{ +if (mmu->features->has_cache_leaf_nodes) +return mmu->is_leaf ? false : true; +else +return true;/* older IPMMU hardware treated as single root */ +} + +static struct ipmmu_vmsa_device *ipmmu_find_root (struct ipmmu_vmsa_device *leaf) +{ +struct ipmmu_vmsa_device *mmu =NULL ; + +if (ipmmu_is_root (leaf)) +return leaf; + +spin_lock (&ipmmu_devices_lock); + +list_for_each_entry (mmu, &ipmmu_devices, list) { +if (ipmmu_is_root (mmu)) +break ; + } + +spin_unlock (&ipmmu_devices_lock); +return mmu; +} + +/* ----------------------------------------------------------------------------- * Read/Write Access */
@@ -211,13 +244,13 @@ static void ipmmu_write(struct ipmmu_vmsstatic u32 ipmmu_ctx_read (struct ipmmu_vmsa_domain *domain,unsigned int reg) { -return ipmmu_read (domain->mmu, domain->context_id *IM_CTX_SIZE + reg); +return ipmmu_read (domain->root, domain->context_id *IM_CTX_SIZE + reg); }static void ipmmu_ctx_write (struct ipmmu_vmsa_domain *domain,unsigned int reg,u32 data) { -ipmmu_write (domain->mmu, domain->context_id *IM_CTX_SIZE + reg, data); +ipmmu_write (domain->root, domain->context_id *IM_CTX_SIZE + reg, data); }/* -----------------------------------------------------------------------------
@@ -350,7 +383,7 @@ static int ipmmu_domain_init_context(str* TODO: Add support for coherent walk through CCI with DVM and remove * cache handling. For now, delegate it to the io-pgtable code. */ - domain->cfg.iommu_dev = domain->mmu->dev; + domain->cfg.iommu_dev = domain->root->dev; domain->iop =alloc_io_pgtable_ops (ARM_32_LPAE_S1 , &domain->cfg, domain);
@@ -360,7 +393,7 @@ static int ipmmu_domain_init_context(str/* * Find an unused context. */ - ret =ipmmu_domain_allocate_context (domain->mmu, domain); + ret =ipmmu_domain_allocate_context (domain->root, domain);if (ret ==IPMMU_CTX_MAX ) {free_io_pgtable_ops (domain->iop);return -EBUSY ;
@@ -431,7 +464,7 @@ static void ipmmu_domain_destroy_context*/ ipmmu_ctx_write (domain,IMCTR ,IMCTR_FLUSH );ipmmu_tlb_sync (domain); -ipmmu_domain_free_context (domain->mmu, domain->context_id); +ipmmu_domain_free_context (domain->root, domain->context_id); }/* -----------------------------------------------------------------------------
@@ -544,7 +577,7 @@ static int ipmmu_attach_device(struct io struct device *dev) {struct ipmmu_vmsa_archdata *archdata = dev->archdata.iommu; -struct ipmmu_vmsa_device *mmu = archdata->mmu; +struct ipmmu_vmsa_device *root, *mmu = archdata->mmu;struct ipmmu_vmsa_domain *domain =to_vmsa_domain (io_domain);unsigned long flags;unsigned int i;
@@ -555,11 +588,18 @@ static int ipmmu_attach_device(struct ioreturn -ENXIO ; } + root =ipmmu_find_root (archdata->mmu); +if (!root) { +dev_err (dev,"Unable to locate root IPMMU\n" ); +return -EAGAIN ; + } +spin_lock_irqsave (&domain->lock, flags);if (!domain->mmu) {/* The domain hasn't been used yet, initialize it. */ domain->mmu = mmu; + domain->root = root; ret =ipmmu_domain_init_context (domain); }else if (domain->mmu != mmu) {/*
@@ -935,6 +975,7 @@ static void ipmmu_device_reset(struct ipstatic const struct ipmmu_features ipmmu_features_default = { .use_ns_alias_offset = true, + .has_cache_leaf_nodes = false, };static const struct of_device_id ipmmu_of_ids[] = {
@@ -994,19 +1035,31 @@ static int ipmmu_probe(struct platform_d mmu->base +=IM_NS_ALIAS_OFFSET ; irq =platform_get_irq (pdev,0 ); -if (irq <0 ) { -dev_err (&pdev->dev,"no IRQ found\n" ); -return irq; - } - ret =devm_request_irq (&pdev->dev, irq, ipmmu_irq,0 , -dev_name (&pdev->dev), mmu); -if (ret <0 ) { -dev_err (&pdev->dev,"failed to request IRQ %d\n" , irq); -return ret; - } +/* +* Determine if this IPMMU instance is a leaf device by checking +* if the renesas,ipmmu-main property exists or not. +*/ +if (mmu->features->has_cache_leaf_nodes && +of_find_property (pdev->dev.of_node,"renesas,ipmmu-main" ,NULL )) + mmu->is_leaf = true; + +/* Root devices have mandatory IRQs */ +if (ipmmu_is_root (mmu)) { +if (irq <0 ) { +dev_err (&pdev->dev,"no IRQ found\n" ); +return irq; + } -ipmmu_device_reset (mmu); + ret =devm_request_irq (&pdev->dev, irq, ipmmu_irq,0 , +dev_name (&pdev->dev), mmu); +if (ret <0 ) { +dev_err (&pdev->dev,"failed to request IRQ %d\n" , irq); +return ret; + } + +ipmmu_device_reset (mmu); + }/* * We can't create the ARM mapping here as it requires the bus to have
PATCH v2 3/11 iommu/ipmmu-vmsa: Enable multi context support
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
Add support for up to 8 contexts. Each context is mapped to one domain. One domain is associated with each device, however one or more uTLBs for a single device are kept in the same domain.
---
Changes since V1:
- Support up to 8 contexts instead of 4
- Use feature flag and runtime handling
- Default to single context
drivers/iommu/ipmmu-vmsa.c | 38 ++++++++++++++++++++++++++++++-------- 1 file changed, 30 insertions(+), 8 deletions(-)
drivers/iommu/ipmmu-vmsa.c +30 -8
@@ -30,11 +30,12 @@#include "io-pgtable.h" -#define IPMMU_CTX_MAX 1 +#define IPMMU_CTX_MAX 8struct ipmmu_features {bool use_ns_alias_offset;bool has_cache_leaf_nodes; +bool has_eight_ctx; };struct ipmmu_vmsa_device {
@@ -44,6 +45,7 @@ struct ipmmu_vmsa_device {const struct ipmmu_features *features;bool is_leaf;unsigned int num_utlbs; +unsigned int num_ctx;spinlock_t lock;/* Protects ctx and domains[] */ DECLARE_BITMAP (ctx,IPMMU_CTX_MAX );struct ipmmu_vmsa_domain *domains[IPMMU_CTX_MAX ];
@@ -347,11 +349,12 @@ static int ipmmu_domain_allocate_contextspin_lock_irqsave (&mmu->lock, flags); - ret =find_first_zero_bit (mmu->ctx,IPMMU_CTX_MAX ); -if (ret !=IPMMU_CTX_MAX ) { + ret =find_first_zero_bit (mmu->ctx, mmu->num_ctx); +if (ret != mmu->num_ctx) { mmu->domains[ret] = domain;set_bit (ret, mmu->ctx); - } + }else + ret = -EBUSY ;spin_unlock_irqrestore (&mmu->lock, flags);
@@ -394,9 +397,9 @@ static int ipmmu_domain_init_context(str* Find an unused context. */ ret =ipmmu_domain_allocate_context (domain->root, domain); -if (ret ==IPMMU_CTX_MAX ) { +if (ret <0 ) {free_io_pgtable_ops (domain->iop); -return -EBUSY ; +return ret; } domain->context_id = ret;
@@ -531,7 +534,7 @@ static irqreturn_t ipmmu_irq(int irq, vo/* * Check interrupts for all active contexts. */ -for (i =0 ; i <IPMMU_CTX_MAX ; i++) { +for (i =0 ; i < mmu->num_ctx; i++) {if (!mmu->domains[i])continue ;if (ipmmu_domain_irq (mmu->domains[i]) ==IRQ_HANDLED )
@@ -601,6 +604,13 @@ static int ipmmu_attach_device(struct io domain->mmu = mmu; domain->root = root; ret =ipmmu_domain_init_context (domain); +if (ret <0 ) { +dev_err (dev,"Unable to initialize IPMMU context\n" ); + domain->mmu =NULL ; + }else { +dev_info (dev,"Using IPMMU context %u\n" , + domain->context_id); + } }else if (domain->mmu != mmu) {/* * Something is wrong, we can't attach two devices using
@@ -969,13 +979,14 @@ static void ipmmu_device_reset(struct ipunsigned int i;/* Disable all contexts. */ -for (i =0 ; i <4 ; ++i) +for (i =0 ; i < mmu->num_ctx; ++i)ipmmu_write (mmu, i *IM_CTX_SIZE +IMCTR ,0 ); }static const struct ipmmu_features ipmmu_features_default = { .use_ns_alias_offset = true, .has_cache_leaf_nodes = false, + .has_eight_ctx = false, };static const struct of_device_id ipmmu_of_ids[] = {
@@ -1034,6 +1045,17 @@ static int ipmmu_probe(struct platform_dif (mmu->features->use_ns_alias_offset) mmu->base +=IM_NS_ALIAS_OFFSET ; +/* +* The number of contexts varies with generation and instance. +* Newer SoCs get a total of 8 contexts enabled, older ones just one. +*/ +if (mmu->features->has_eight_ctx) + mmu->num_ctx =8 ; +else + mmu->num_ctx =1 ; + +WARN_ON (mmu->num_ctx >IPMMU_CTX_MAX ); + irq =platform_get_irq (pdev,0 );/*
PATCH v2 4/11 iommu/ipmmu-vmsa: Reuse iommu groups
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
Extend the IPMMU driver to group devices together based on the IPMMU device they are connected to. The slave devices are kept on a list which is used to determine if existing groups (and contexts) exist.
With this patch the two SYS-DMAC devices using IPMMU-DS0 on r8a7795 will be grouped together.
---
Changes since V1:
- New patch
drivers/iommu/ipmmu-vmsa.c | 68 ++++++++++++++++++++++++++++++++++++++------ 1 file changed, 60 insertions(+), 8 deletions(-)
drivers/iommu/ipmmu-vmsa.c +60 -8
@@ -69,11 +69,16 @@ struct ipmmu_vmsa_archdata {struct ipmmu_vmsa_device *mmu;unsigned int *utlbs;unsigned int num_utlbs; +struct device *dev; +struct list_head list; };static DEFINE_SPINLOCK (ipmmu_devices_lock);static LIST_HEAD (ipmmu_devices); +static DEFINE_SPINLOCK (ipmmu_slave_devices_lock); +static LIST_HEAD (ipmmu_slave_devices); +static struct ipmmu_vmsa_domain *to_vmsa_domain (struct iommu_domain *dom) { return container_of(dom, struct ipmmu_vmsa_domain, io_domain);
@@ -619,6 +624,9 @@ static int ipmmu_attach_device(struct iodev_err (dev,"Can't attach IPMMU %s to domain on IPMMU %s\n" ,dev_name (mmu->dev),dev_name (domain->mmu->dev)); ret = -EINVAL ; + }else { +dev_info (dev,"Reusing IPMMU context %u\n" , + domain->context_id); }spin_unlock_irqrestore (&domain->lock, flags);
@@ -676,6 +684,42 @@ static phys_addr_t ipmmu_iova_to_phys(streturn domain->iop->iova_to_phys (domain->iop, iova); } +static struct device *ipmmu_find_sibling_device (struct device *dev) +{ +struct ipmmu_vmsa_archdata *archdata = dev->archdata.iommu; +struct ipmmu_vmsa_archdata *sibling_archdata =NULL ; +bool found = false; + +spin_lock (&ipmmu_slave_devices_lock); + +list_for_each_entry (sibling_archdata, &ipmmu_slave_devices, list) { +if (archdata == sibling_archdata) +continue ; +if (sibling_archdata->mmu == archdata->mmu) { + found = true; +break ; + } + } + +spin_unlock (&ipmmu_slave_devices_lock); + +return found ? sibling_archdata->dev :NULL ; +} + +static struct iommu_group *ipmmu_find_group (struct device *dev) +{ +struct iommu_group *group; +struct device *sibling; + + sibling =ipmmu_find_sibling_device (dev); +if (sibling) + group =iommu_group_get (sibling); +if (!sibling ||IS_ERR (group)) + group =generic_device_group (dev); + +return group; +} +static int ipmmu_find_utlbs (struct ipmmu_vmsa_device *mmu,struct device *dev,unsigned int *utlbs,unsigned int num_utlbs) {
@@ -756,6 +800,7 @@ static int ipmmu_init_platform_device(st archdata->mmu = mmu; archdata->utlbs = utlbs; archdata->num_utlbs = num_utlbs; + archdata->dev = dev; dev->archdata.iommu = archdata;return 0 ;
@@ -908,6 +953,7 @@ static void ipmmu_domain_free_dma(structstatic int ipmmu_add_device_dma (struct device *dev) { +struct ipmmu_vmsa_archdata *archdata = dev->archdata.iommu;struct iommu_group *group;/* only accept devices with iommus property */
@@ -919,11 +965,21 @@ static int ipmmu_add_device_dma(struct dif (IS_ERR (group))return PTR_ERR (group); + archdata = dev->archdata.iommu; +spin_lock (&ipmmu_slave_devices_lock); +list_add (&archdata->list, &ipmmu_slave_devices); +spin_unlock (&ipmmu_slave_devices_lock);return 0 ; }static void ipmmu_remove_device_dma (struct device *dev) { +struct ipmmu_vmsa_archdata *archdata = dev->archdata.iommu; + +spin_lock (&ipmmu_slave_devices_lock); +list_del (&archdata->list); +spin_unlock (&ipmmu_slave_devices_lock); +iommu_group_remove_device (dev); }
@@ -932,15 +988,11 @@ static struct iommu_group *ipmmu_device_struct iommu_group *group;int ret; - group =generic_device_group (dev); -if (IS_ERR (group)) -return group; - - ret =ipmmu_init_platform_device (dev, group); -if (ret) { -iommu_group_put (group); + ret =ipmmu_init_platform_device (dev,NULL ); +if (!ret) + group =ipmmu_find_group (dev); +else group =ERR_PTR (ret); - }return group; }
PATCH v2 5/11 iommu/ipmmu-vmsa: Make use of IOMMU_OF_DECLARE()
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
Hook up IOMMU_OF_DECLARE() support in case CONFIG_IOMMU_DMA is enabled. The only current supported case for 32-bit ARM is disabled, however for 64-bit ARM this is required.
---
Changes since V1:
- Reworked slightly to fit updated patch order and [PATCH v3 00/06] iommu/ipmmu-vmsa: IPMMU multi-arch update V3
drivers/iommu/ipmmu-vmsa.c | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
drivers/iommu/ipmmu-vmsa.c +26 -0
@@ -19,6 +19,7 @@#include <linux/iommu.h> #include <linux/module.h> #include <linux/of.h> +#include <linux/of_iommu.h> #include <linux/platform_device.h> #include <linux/sizes.h> #include <linux/slab.h>
@@ -1178,15 +1179,22 @@ static struct platform_driver ipmmu_drivstatic int __init ipmmu_init (void ) { +static bool setup_done;int ret; +if (setup_done) +return 0 ; + ret =platform_driver_register (&ipmmu_driver);if (ret <0 )return ret; +#if defined(CONFIG_ARM ) && !defined(CONFIG_IOMMU_DMA )if (!iommu_present (&platform_bus_type))bus_set_iommu (&platform_bus_type, &ipmmu_ops); +#endif + setup_done = true;return 0 ; }
@@ -1198,6 +1206,24 @@ static void __exit ipmmu_exit(void)subsys_initcall (ipmmu_init);module_exit (ipmmu_exit); +#ifdef CONFIG_IOMMU_DMA +static int __init ipmmu_vmsa_iommu_of_setup (struct device_node *np) +{ +static const struct iommu_ops *ops = &ipmmu_ops; + +ipmmu_init (); + +of_iommu_set_ops (np, (struct iommu_ops *)ops); +if (!iommu_present (&platform_bus_type)) +bus_set_iommu (&platform_bus_type, ops); + +return 0 ; +} + +IOMMU_OF_DECLARE (ipmmu_vmsa_iommu_of,"renesas,ipmmu-vmsa" , + ipmmu_vmsa_iommu_of_setup); +#endif +MODULE_DESCRIPTION ("IOMMU API for Renesas VMSA-compatible IPMMU" );MODULE_AUTHOR ("Laurent Pinchart <laurent.pinchart-ryLnwIuWjnjg/[email protected]>" );MODULE_LICENSE ("GPL v2" );
Re: [PATCH v2 05/11] iommu/ipmmu-vmsa: Make use of IOMMU_OF_DECLARE()
Hi Magnus,
Quoted 18 lines · Magnus Damm
From: Magnus Damm <[email protected]>
Hook up
IOMMU_OF_DECLARE()support in caseCONFIG_IOMMU_DMAis enabled. The only current supported case for 32-bit ARM is disabled, however for 64-bit ARM this is required.Signed-off-by Magnus Damm <[email protected]>---
Changes since V1:
- Reworked slightly to fit updated patch order and [PATCH v3 00/06] iommu/ipmmu-vmsa: IPMMU multi-arch update V3drivers/iommu/ipmmu-vmsa.c | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+)
drivers/iommu/ipmmu-vmsa.c 2016-06-06 10:57:26.790607110 +0900
Quoted 9 lines
drivers/iommu/ipmmu-vmsa.c 2016-06-06 10:57:26.790607110 +0900 renamed from drivers/iommu/ipmmu-vmsa.c +8
-0+#ifdef CONFIG_IOMMU_DMA +static int __init ipmmu_vmsa_iommu_of_setup(struct device_node *np) +{ + static const struct iommu_ops *ops = &ipmmu_ops; + + ipmmu_init(); + + of_iommu_set_ops(np, (struct iommu_ops *)ops);
As of commit 65e251a4634c5644 ("iommu: Drop the of_iommu_{set/get}_ops() interface"), this should become:
iommu_register_instance(&np->fwnode, (struct iommu_ops *)ops);
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
PATCH v2 6/11 iommu/ipmmu-vmsa: Teach xlate() to skip disabled iommus
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
The ->xlate() call gets invoked even though the iommu device has status = "disabled" in DT, so make sure we skip over disabled devices.
In my mind it would make sense to have this at some shared level, but I guess some users may want to configure the iommu regardless of DT state.
---
Changes since V1:
- Reworked slightly to fit on top of updated patch order
drivers/iommu/ipmmu-vmsa.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/iommu/ipmmu-vmsa.c +7 -1
@@ -1001,7 +1001,13 @@ static struct iommu_group *ipmmu_device_static int ipmmu_of_xlate_dma (struct device *dev,struct of_phandle_args *spec) { -/* dummy callback to satisfy of_iommu_configure() */ +/* If the IPMMU device is disabled in DT then return error +* to make sure the of_iommu code does not install ops +* even though the iommu device is disabled +*/ +if (!of_device_is_available (spec->np)) +return -ENODEV ; +return 0 ; }
Re: [PATCH v2 06/11] iommu/ipmmu-vmsa: Teach xlate() to skip disabled iommus
Hi Magnus,
Thank you for the patch.
I agree with the comment that Geert made on v1, and I haven't seen you replying to it or addressing it.
Quoting Geert,
"I think this should be handled in drivers/iommu/of_iommu.c:of_iommu_init() instead, cfr. commit 3e5dd6f6e690048d ("clk: Ignore disabled DT clock providers")."
Quoted 35 lines · On Monday 06 Jun 2016 12:58:22 Magnus Damm wrote:
From: Magnus Damm <[email protected]>
The ->xlate() call gets invoked even though the iommu device has status = "disabled" in DT, so make sure we skip over disabled devices.
In my mind it would make sense to have this at some shared level, but I guess some users may want to configure the iommu regardless of DT state.
Signed-off-by Magnus Damm <[email protected]>---
Changes since V1:
- Reworked slightly to fit on top of updated patch orderdrivers/iommu/ipmmu-vmsa.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)drivers/iommu/ipmmu-vmsa.c +7
-1@@ -1001,7 +1001,13 @@ static struct iommu_group *ipmmu_device_static int ipmmu_of_xlate_dma (struct device *dev,struct of_phandle_args *spec) { -/* dummy callback to satisfy of_iommu_configure() */ +/* If the IPMMU device is disabled in DT then return error +* to make sure the of_iommu code does not install ops +* even though the iommu device is disabled +*/ +if (!of_device_is_available (spec->np)) +return -ENODEV ; +return 0 ; }
Signature · 3 lines
Regards, Laurent Pinchart
PATCH v2 7/11 iommu/ipmmu-vmsa: IPMMU device is 64-bit bus master
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
The r8a7795 IPMMU supports 64-bit bus mastering. Both the coherent DMA mask and the streaming DMA mask are set to unlock the 64-bit address space for coherent allocations and streaming operations.
---
Changes since V1:
- Updated the commit message
drivers/iommu/ipmmu-vmsa.c | 1 + 1 file changed, 1 insertion(+)
drivers/iommu/ipmmu-vmsa.c +1 -0
@@ -1082,6 +1082,7 @@ static int ipmmu_probe(struct platform_dspin_lock_init (&mmu->lock);bitmap_zero (mmu->ctx,IPMMU_CTX_MAX ); mmu->features = match->data; +dma_set_mask_and_coherent (&pdev->dev,DMA_BIT_MASK (64 ));/* Map I/O memory and request IRQ. */ res =platform_get_resource (pdev,IORESOURCE_MEM ,0 );
PATCH v2 8/11 iommu/ipmmu-vmsa: Write IMCTR twice
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
Write IMCTR both in the root device and the leaf node.
---
Changes since V1:
- None
drivers/iommu/ipmmu-vmsa.c | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)
drivers/iommu/ipmmu-vmsa.c +14 -3
@@ -261,6 +261,16 @@ static void ipmmu_ctx_write(struct ipmmuipmmu_write (domain->root, domain->context_id *IM_CTX_SIZE + reg, data); } +static void ipmmu_ctx_write2 (struct ipmmu_vmsa_domain *domain,unsigned int reg, +u32 data) +{ +if (domain->mmu != domain->root) +ipmmu_write (domain->mmu, + domain->context_id *IM_CTX_SIZE + reg, data); + +ipmmu_write (domain->root, domain->context_id *IM_CTX_SIZE + reg, data); +} +/* ----------------------------------------------------------------------------- * TLB and microTLB Management */
@@ -287,7 +297,7 @@ static void ipmmu_tlb_invalidate(struct reg =ipmmu_ctx_read (domain,IMCTR ); reg |=IMCTR_FLUSH ; -ipmmu_ctx_write (domain,IMCTR , reg); +ipmmu_ctx_write2 (domain,IMCTR , reg);ipmmu_tlb_sync (domain); }
@@ -445,7 +455,8 @@ static int ipmmu_domain_init_context(str* software management as we have no use for it. Flush the TLB as * required when modifying the context registers. */ -ipmmu_ctx_write (domain,IMCTR ,IMCTR_INTEN |IMCTR_FLUSH |IMCTR_MMUEN ); +ipmmu_ctx_write2 (domain,IMCTR , +IMCTR_INTEN |IMCTR_FLUSH |IMCTR_MMUEN );return 0 ; }
@@ -471,7 +482,7 @@ static void ipmmu_domain_destroy_context* * TODO: Is TLB flush really needed ? */ -ipmmu_ctx_write (domain,IMCTR ,IMCTR_FLUSH ); +ipmmu_ctx_write2 (domain,IMCTR ,IMCTR_FLUSH );ipmmu_tlb_sync (domain);ipmmu_domain_free_context (domain->root, domain->context_id); }
PATCH v2 9/11 iommu/ipmmu-vmsa: Make IMBUSCTR setup optional
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
Introduce a feature to allow opt-out of setting up IMBUSCR. The default case is unchanged.
---
Changes since V1:
- Updated the commit message
- Reworked patch to coexist with the multi context feature
drivers/iommu/ipmmu-vmsa.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
drivers/iommu/ipmmu-vmsa.c +6 -4
@@ -37,6 +37,7 @@ struct ipmmu_features {bool use_ns_alias_offset;bool has_cache_leaf_nodes;bool has_eight_ctx; +bool setup_imbuscr; };struct ipmmu_vmsa_device {
@@ -438,10 +439,10 @@ static int ipmmu_domain_init_context(stripmmu_ctx_write (domain,IMMAIR0 , domain->cfg.arm_lpae_s1_cfg.mair[0 ]);/* IMBUSCR */ -ipmmu_ctx_write (domain,IMBUSCR , -ipmmu_ctx_read (domain,IMBUSCR ) & - ~(IMBUSCR_DVM |IMBUSCR_BUSSEL_MASK )); - +if (domain->root->features->setup_imbuscr) +ipmmu_ctx_write (domain,IMBUSCR , +ipmmu_ctx_read (domain,IMBUSCR ) & + ~(IMBUSCR_DVM |IMBUSCR_BUSSEL_MASK ));/* * IMSTR * Clear all interrupt flags.
@@ -1057,6 +1058,7 @@ static const struct ipmmu_features ipmmu .use_ns_alias_offset = true, .has_cache_leaf_nodes = false, .has_eight_ctx = false, + .setup_imbuscr = true, };static const struct of_device_id ipmmu_of_ids[] = {
PATCH v2 10/11 iommu/ipmmu-vmsa: Allow two bit SL0
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
Introduce support for two bit SL0 bitfield in IMTTBCR by using a separate feature flag.
---
Changes since V1:
- None
drivers/iommu/ipmmu-vmsa.c | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-)
drivers/iommu/ipmmu-vmsa.c +14 -1
@@ -38,6 +38,7 @@ struct ipmmu_features {bool has_cache_leaf_nodes;bool has_eight_ctx;bool setup_imbuscr; +bool twobit_imttbcr_sl0; };struct ipmmu_vmsa_device {
@@ -146,6 +147,10 @@ static struct ipmmu_vmsa_domain *to_vmsa#define IMTTBCR_TSZ0_MASK (7 << 0)#define IMTTBCR_TSZ0_SHIFT O +#define IMTTBCR_SL0_TWOBIT_LVL_3 (0 << 6) +#define IMTTBCR_SL0_TWOBIT_LVL_2 (1 << 6) +#define IMTTBCR_SL0_TWOBIT_LVL_1 (2 << 6) +#define IMBUSCR 0x000c#define IMBUSCR_DVM (1 << 2)#define IMBUSCR_BUSSEL_SYS (0 << 0)
@@ -381,6 +386,7 @@ static int ipmmu_domain_allocate_contextstatic int ipmmu_domain_init_context (struct ipmmu_vmsa_domain *domain) {u64 ttbr; +u32 tmp;int ret;/*
@@ -431,9 +437,15 @@ static int ipmmu_domain_init_context(str* We use long descriptors with inner-shareable WBWA tables and allocate * the whole 32-bit VA space to TTBR0. */ + +if (domain->root->features->twobit_imttbcr_sl0) + tmp =IMTTBCR_SL0_TWOBIT_LVL_1 ; +else + tmp =IMTTBCR_SL0_LVL_1 ; +ipmmu_ctx_write (domain,IMTTBCR ,IMTTBCR_EAE |IMTTBCR_SH0_INNER_SHAREABLE |IMTTBCR_ORGN0_WB_WA | -IMTTBCR_IRGN0_WB_WA |IMTTBCR_SL0_LVL_1 ); +IMTTBCR_IRGN0_WB_WA | tmp);/* MAIR0 */ ipmmu_ctx_write (domain,IMMAIR0 , domain->cfg.arm_lpae_s1_cfg.mair[0 ]);
@@ -1059,6 +1071,7 @@ static const struct ipmmu_features ipmmu .has_cache_leaf_nodes = false, .has_eight_ctx = false, .setup_imbuscr = true, + .twobit_imttbcr_sl0 = false, };static const struct of_device_id ipmmu_of_ids[] = {
PATCH v2 11/11 iommu/ipmmu-vmsa: Hook up r8a7795 DT matching code
In reply to Magnus DammFrom: Magnus Damm <[email protected]>
Tie in r8a7795 features and update the IOMMU_OF_DECLARE compat string to hook up the updated compat string.
TODO:
- Go over init order once more
- Consider counting number of IPMMU devices from ->xlate()
- Experiment with delaying call to bus_set_iommu()
---
Changes since V1:
- Enable multi context feature
- Update TODO list
drivers/iommu/ipmmu-vmsa.c | 13 +++++++++++++ 1 file changed, 13 insertions(+)
drivers/iommu/ipmmu-vmsa.c +13 -0
@@ -1074,11 +1074,22 @@ static const struct ipmmu_features ipmmu .twobit_imttbcr_sl0 = false, }; +static const struct ipmmu_features ipmmu_features_r8a7795 = { + .use_ns_alias_offset = false, + .has_cache_leaf_nodes = true, + .has_eight_ctx = true, + .setup_imbuscr = false, + .twobit_imttbcr_sl0 = true, +}; +static const struct of_device_id ipmmu_of_ids[] = { { .compatible ="renesas,ipmmu-vmsa" , .data = &ipmmu_features_default, }, { + .compatible ="renesas,ipmmu-r8a7795" , + .data = &ipmmu_features_r8a7795, + }, {/* Terminator */ }, };
@@ -1255,6 +1266,8 @@ static int __init ipmmu_vmsa_iommu_of_seIOMMU_OF_DECLARE (ipmmu_vmsa_iommu_of,"renesas,ipmmu-vmsa" , ipmmu_vmsa_iommu_of_setup); +IOMMU_OF_DECLARE (ipmmu_r8a7795_iommu_of,"renesas,ipmmu-r8a7795" , + ipmmu_vmsa_iommu_of_setup);#endif MODULE_DESCRIPTION ("IOMMU API for Renesas VMSA-compatible IPMMU" );
Hi Magnus,
Quoted 13 lines · Magnus Damm
iommu/ipmmu-vmsa: r8a7795 support V2
[PATCH v2 01/11] iommu/ipmmu-vmsa: Introduce features, break out alias [PATCH v2 02/11] iommu/ipmmu-vmsa: Add optional root device feature [PATCH v2 03/11] iommu/ipmmu-vmsa: Enable multi context support [PATCH v2 04/11] iommu/ipmmu-vmsa: Reuse iommu groups
[PATCH v2 05/11] iommu/ipmmu-vmsa: Make use ofIOMMU_OF_DECLARE()[PATCH v2 06/11] iommu/ipmmu-vmsa: Teachxlate()to skip disabled iommus [PATCH v2 07/11] iommu/ipmmu-vmsa: IPMMU device is 64-bit bus master [PATCH v2 08/11] iommu/ipmmu-vmsa: Write IMCTR twice
[PATCH v2 09/11] iommu/ipmmu-vmsa: Make IMBUSCTR setup optional [PATCH v2 10/11] iommu/ipmmu-vmsa: Allow two bit SL0
[PATCH v2 11/11] iommu/ipmmu-vmsa: Hook up r8a7795 DT matching code
Thanks for your series!
For your convenience, I've queued it up in topic/r8a7795-ipmmu-v2 at
https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git, and will include it in next renesas-drivers release.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Joerg Roedel
maintainerQuoted 5 lines · Magnus Damm
Developed on top of next-20160602 and:
[PATCH v3 00/06] iommu/ipmmu-vmsa: IPMMU multi-arch update V3drivers/iommu/ipmmu-vmsa.c | 318 +++++++++++++++++++++++++++++++++++++------- 1 file changed, 269 insertions(+), 49 deletions(-)
Okay, what is the plan on merging this? It is developed on linux-next and doesn't apply on v4.7-rc4. From the areas it touches it should go through the iommu-tree, unless there are good reasons not to.
Joerg
P.S.: Same question applies to your other two patch-sets.