| Message ID | 20200710160131.9.I667d728b2a99b1ed50df01a3e14483fa69babf0e@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/arm/boot/dts/qcom-msm8974.dtsi b/arch/arm/boot/dts/qcom-msm8974.dtsi index 51f5f904f9eb..9f84c9fd716c 100644 --- a/arch/arm/boot/dts/qcom-msm8974.dtsi +++ b/arch/arm/boot/dts/qcom-msm8974.dtsi @@ -1402,7 +1402,7 @@ cnoc: interconnect@fc480000 { mdss: mdss@fd900000 { status = "disabled"; - compatible = "qcom,mdss"; + compatible = "qcom,mdss", "simple-bus"; reg = <0xfd900000 0x100>, <0xfd924000 0x1000>; reg-names = "mdss_phys",
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/arm/boot/dts/qcom-msm8974.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)