From mboxrd@z Thu Jan 1 00:00:00 1970 From: john.garry@huawei.com (John Garry) Date: Wed, 23 Aug 2017 14:17:24 +0100 Subject: [PATCH v6 3/3] iommu/arm-smmu-v3:Enable ACPI based HiSilicon erratum 161010801 In-Reply-To: <5FC3163CFD30C246ABAA99954A238FA8383CC287@FRAEML521-MBX.china.huawei.com> References: <20170809100715.870516-1-shameerali.kolothum.thodi@huawei.com> <20170809100715.870516-4-shameerali.kolothum.thodi@huawei.com> <20170810172723.GD9980@arm.com> <5FC3163CFD30C246ABAA99954A238FA8383CC287@FRAEML521-MBX.china.huawei.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org >>> Signed-off-by: Shameer Kolothum >> >>> --- >>> drivers/iommu/arm-smmu-v3.c | 27 ++++++++++++++++++++++----- >>> 1 file changed, 22 insertions(+), 5 deletions(-) >> >> Please can you also add a devicetree binding with corresponding >> documentation to enable this workaround on non-ACPI based systems too? >> It should be straightforward if you update the arm_smmu_options table. > > As I mentioned before, devicetree was a lower priority and we would definitely > submit patch to support that. Even if we update the arm_smmu_options table > with DT binding, the generic function to retrieve the MSI address regions only > works on ACPI/IORT case now. > Hi Will, Can you confirm your stance on supporting this workaround for DT as well as ACPI? For us, we now only "officially" support ACPI FW, and DT support at this point is patchy/limited. To me, adding DT support is just more errata workaround code to maintain with little useful gain. Thanks very much, John > Moreover I am on holidays starting tomorrow, and really appreciate if this series > can go through now. > > Please let me know. > > Thanks, > Shameer > > . >