> -----Original Message----- > From: [email protected] [mailto:iommu- > [email protected]] On Behalf Of Antonios Motakis > Sent: Thursday, June 05, 2014 10:33 PM > To: [email protected]; [email protected]; > [email protected] > Cc: [email protected]; [email protected]; open list; > [email protected]; [email protected]; Yoder Stuart-B08248; > moderated list:ARM SMMU DRIVER; Antonios Motakis; > [email protected]; [email protected] > Subject: [RFC PATCH v6 04/20] iommu/arm-smmu: add capability > IOMMU_CAP_INTR_REMAP > > With an ARM SMMU, interrupt remapping should always be safe from the > SMMU's point of view, as it is properly handled by the GIC. > > Signed-off-by: Antonios Motakis <[email protected]> > --- > drivers/iommu/arm-smmu.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/iommu/arm-smmu.c b/drivers/iommu/arm-smmu.c index > 15ab2af..ff29402 100644 > --- a/drivers/iommu/arm-smmu.c > +++ b/drivers/iommu/arm-smmu.c > @@ -1544,7 +1544,7 @@ static int arm_smmu_domain_has_cap(struct > iommu_domain *domain, > if (smmu_domain->root_cfg.smmu->features & > ARM_SMMU_FEAT_COHERENT_WALK) > caps |= IOMMU_CAP_CACHE_COHERENCY; > > - caps |= IOMMU_CAP_NOEXEC; > + caps |= IOMMU_CAP_NOEXEC | IOMMU_CAP_INTR_REMAP; > > return !!(cap & caps); > } Why mention this as an IOMMU capability when IOMMU doesn't support it? Also, wouldn't this depend on the GIC IP version? What are we gaining by adding this IOMMU capability list?
-Varun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
