The iommu mapping for S2 SIDs are taken care by TrustZone. For the targets which does not have the support of TrustZone, these mappings need to be created in the driver using an iommu domain. Leaving these SIDs unconfigured will result in a global smmu fault. Hence configuring them for Non-TrustZone targets is mandatory. Changes from v1: - Rebase and fix compilation errors on latest ath10k tree tip Rakesh Pillai (3): dt-bindings: ath10k: Add wifi-firmware subnode for wifi node ath10k: Setup the msa resources before qmi init ath10k: Add support for targets without trustzone .../bindings/net/wireless/qcom,ath10k.txt | 14 ++ drivers/net/wireless/ath/ath10k/core.h | 5 + drivers/net/wireless/ath/ath10k/qmi.c | 61 +------ drivers/net/wireless/ath/ath10k/qmi.h | 3 - drivers/net/wireless/ath/ath10k/snoc.c | 182 ++++++++++++++++++++- drivers/net/wireless/ath/ath10k/snoc.h | 7 + 6 files changed, 208 insertions(+), 64 deletions(-) -- 2.7.4
