On Wed, Mar 25, 2026 at 5:52 PM Krzysztof Kozlowski <[email protected]> wrote: > > Device node has children with MMIO addressing, so must have ranges: > > msm/qcom,qcm2290-mdss.example.dtb: display-subsystem@5e00000 > (qcom,qcm2290-mdss): 'ranges' is a required property > > Fixes: 966a08c293cb ("dt-bindings: display: msm: qcm2290-mdss: Fix iommus > property") > Signed-off-by: Krzysztof Kozlowski <[email protected]> > > --- > > Fix for commit taken by Bjorn (Qualcomm SoC). > --- > .../devicetree/bindings/display/msm/qcom,qcm2290-mdss.yaml | 1 + > 1 file changed, 1 insertion(+) > > diff --git > a/Documentation/devicetree/bindings/display/msm/qcom,qcm2290-mdss.yaml > b/Documentation/devicetree/bindings/display/msm/qcom,qcm2290-mdss.yaml > index 2772cdec7e42..bb09ecd1a5b4 100644 > --- a/Documentation/devicetree/bindings/display/msm/qcom,qcm2290-mdss.yaml > +++ b/Documentation/devicetree/bindings/display/msm/qcom,qcm2290-mdss.yaml > @@ -108,6 +108,7 @@ examples: > "cpu-cfg"; > > iommus = <&apps_smmu 0x420 0x2>; > + ranges;
Ah, it was surely an oversight on my part, FWIW: Reviewed-by: Sumit Garg <[email protected]> -Sumit > > display-controller@5e01000 { > compatible = "qcom,qcm2290-dpu"; > -- > 2.51.0 >
