When display patches were initially submitted, they did not include the p2, p3, mst2link and mst3link reg ranges. The devicetreedisplay nodes for Glymur are still being reviewed and have not been merged yet.
This fix resulted from review comments on the devicetree nodes. Signed-off-by: Abel Vesa <[email protected]> --- Changes in v3: - Fixed the reg ranges in the example node in qcom,glymur-mdss.yaml as well. - Link to v2: https://patch.msgid.link/20260302-glymur-fix-dp-bindings-reg-clocks-v2-0-e99b6f871...@oss.qualcomm.com Changes in v2: - mistakenly sent without cover subject line. Please ignore. - Link to v1: https://patch.msgid.link/20260227-glymur-fix-dp-bindings-reg-clocks-v1-1-99f7b42b4...@oss.qualcomm.com --- Abel Vesa (2): dt-bindings: display: msm: Fix reg ranges and clocks on Glymur dt-bindings: display: msm: Fix reg ranges for DP example node .../bindings/display/msm/dp-controller.yaml | 21 ++++++++++++++++++++- .../bindings/display/msm/qcom,glymur-mdss.yaml | 16 ++++++++++------ 2 files changed, 30 insertions(+), 7 deletions(-) --- base-commit: 7c21b660e919698b10efa8bdb120f0f9bc3d3832 change-id: 20260227-glymur-fix-dp-bindings-reg-clocks-704d0ccbeef9 Best regards, -- Abel Vesa <[email protected]>
