| Message ID | 20200710160131.6.Ie343c226b3566575fcaa9e4a8732674a1ae1b513@changeid (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | drm/msm: Avoid possible infinite probe deferral and speed booting | expand |
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi index b0d8308a3e95..e52a5e95168a 100644 --- a/arch/arm64/boot/dts/qcom/sdm845.dtsi +++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi @@ -3582,7 +3582,7 @@ clock_camcc: clock-controller@ad00000 { }; mdss: mdss@ae00000 { - compatible = "qcom,sdm845-mdss"; + compatible = "qcom,sdm845-mdss", "simple-bus"; reg = <0 0x0ae00000 0 0x1000>; reg-names = "mdss";
As described in the bindings patch, this means that our child nodes are devices in their own right. Signed-off-by: Douglas Anderson <dianders@chromium.org> --- If this patch lands before the patch ("drm/msm: Avoid manually populating our children if "simple-bus" is there") it doesn't seem to be the end of the world. The first time through add_display_components() it'll notice that the children are already populated and it will be a no-op. When it gets a defer it will then depouplate them (even though it didn't populate them) and future calls will just populate them again. arch/arm64/boot/dts/qcom/sdm845.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)