On Fri, Feb 28, 2014 at 04:17:43PM +0000, Timur Tabi wrote: > On Fri, Feb 21, 2014 at 11:16 AM, Will Deacon <will.dea...@arm.com> wrote: > > > > +- calxeda,smmu-secure-config-access : Enable proper handling of buggy > > + implementations that always use secure access to > > + SMMU configuration registers. In this case non-secure > > + aliases of secure registers have to be used during > > + SMMU configuration. > > I'm confused. Why does this property have a "calxeda" prefix? How is > it a Calxeda-specific property?
Because they wired up their SMMU backwards. It's basically an implementation-specific erratum workaround. Will _______________________________________________ iommu mailing list iommu@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/iommu