Re: [PATCH v2] iommu/arm-smmu-v3: Don't reserve implementation defined register space

2020-05-18 Thread Will Deacon
On Wed, 13 May 2020 13:02:57 +0200, Jean-Philippe Brucker wrote: > Some SMMUv3 implementation embed the Perf Monitor Group Registers (PMCG) > inside the first 64kB region of the SMMU. Since PMCG are managed by a > separate driver, this layout causes resource reservation conflicts > during boot. >

Re: [PATCH v2] iommu/arm-smmu-v3: Don't reserve implementation defined register space

2020-05-13 Thread Robin Murphy
On 2020-05-13 12:02 pm, Jean-Philippe Brucker wrote: Some SMMUv3 implementation embed the Perf Monitor Group Registers (PMCG) inside the first 64kB region of the SMMU. Since PMCG are managed by a separate driver, this layout causes resource reservation conflicts during boot. To avoid this confli

[PATCH v2] iommu/arm-smmu-v3: Don't reserve implementation defined register space

2020-05-13 Thread Jean-Philippe Brucker
Some SMMUv3 implementation embed the Perf Monitor Group Registers (PMCG) inside the first 64kB region of the SMMU. Since PMCG are managed by a separate driver, this layout causes resource reservation conflicts during boot. To avoid this conflict, don't reserve the MMIO regions that are implementat