| Message ID | 20200710160131.8.I7a02e4b37149190227bc03fd1027c8241d8d4f4a@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/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi index 9951286db775..e303b0e644ac 100644 --- a/arch/arm64/boot/dts/qcom/msm8996.dtsi +++ b/arch/arm64/boot/dts/qcom/msm8996.dtsi @@ -499,7 +499,7 @@ mmcc: clock-controller@8c0000 { }; mdss: mdss@900000 { - compatible = "qcom,mdss"; + compatible = "qcom,mdss", "simple-bus"; reg = <0x00900000 0x1000>, <0x009b0000 0x1040>,
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. NOTE: I have no way to test this patch, but I'm assuming it works OK? arch/arm64/boot/dts/qcom/msm8996.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)