From da181156dc7f99bf0068577e957b19fdb5b682eb Mon Sep 17 00:00:00 2001 From: "Isaac J. Manjarres" Date: Tue, 17 Aug 2021 17:37:54 -0700 Subject: [PATCH] ARM: dts: msm: Enable fw_devlink in strict mode for Kalama The FW devlink feature is used so that the kernel can establish supplier-consumer relations between devices based on common properties in the devicetree (e.g. IOMMUs, clocks, and power domains). For example, if a peripheral in the devicetree uses a particular clock, it can express this through the "clocks" property. The kernel will then ensure that the clock device has been successfully bound to its driver before the peripheral can attempt to bind to its own driver. The kernel does not treat all of these dependencies as mandatory however, such as a dependency on an IOMMU, and can allow IOMMU clients to probe before their IOMMU has finished binding to its driver. This is problematic for our systems, as clients upstream of an IOMMU must have their stream IDs (SIDs) programmed into the IOMMU's stream matching registers (SMRs), so that the IOMMU doesn't fault a client's transaction as a transaction with an unidentified stream. Thus enable FW devlink feature in strict mode for Kalama to ensure that IOMMU clients can only probe after their IOMMU device has been bound to a driver. Change-Id: I4000f34967dcdd9698b8e98193e11b1e272a508f --- qcom/kalama.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/qcom/kalama.dtsi b/qcom/kalama.dtsi index fdc43397..9b98cd79 100644 --- a/qcom/kalama.dtsi +++ b/qcom/kalama.dtsi @@ -21,7 +21,7 @@ chosen: chosen { - bootargs = "nokaslr kpti=0 log_buf_len=256K swiotlb=0 loop.max_part=7"; + bootargs = "nokaslr kpti=0 log_buf_len=256K swiotlb=0 loop.max_part=7 fw_devlink.strict=1"; }; reserved_memory: reserved-memory { };