[PATCH 6/9] iommu/arm-smmu: Support buggy implemenations where all config accesses are secure

Will Deacon will.deacon at arm.com
Fri Sep 27 09:05:28 EDT 2013


On Thu, Sep 26, 2013 at 11:36:18PM +0100, Andreas Herrmann wrote:
> In such a case we have to use secure aliases of some non-secure
> registers.
> 
> This behaviour is controlled via a flag in smmu->bugs. It is set
> based on DT information when probing an SMMU device.

:(

I guess my main comment is just some understanding on how things are wired.
It's *just* the configuration access that is secure, right? Device
transactions are non-secure, so the existing TLB invalidation code will work
correctly?

Will



More information about the linux-arm-kernel mailing list