On 10/28/2025 2:54 AM, Bjorn Andersson wrote: > On Fri, Oct 24, 2025 at 01:21:01PM +0800, Xiangxu Yin via B4 Relay wrote: >> From: Xiangxu Yin <[email protected]> >> >> SM6150 uses the same DisplayPort controller as SM8150, which is already >> compatible with SM8350. Add the SM6150-specific compatible string and >> update the binding example accordingly. >> >> Signed-off-by: Xiangxu Yin <[email protected]> >> --- >> .../devicetree/bindings/display/msm/qcom,sm6150-mdss.yaml | 10 >> ++++++++++ >> 1 file changed, 10 insertions(+) >> >> diff --git >> a/Documentation/devicetree/bindings/display/msm/qcom,sm6150-mdss.yaml >> b/Documentation/devicetree/bindings/display/msm/qcom,sm6150-mdss.yaml >> index >> 9ac24f99d3ada1c197c9654dc9babebccae972ed..ba0dea2edea98cee0826cf38b3f33361666e004a >> 100644 >> --- a/Documentation/devicetree/bindings/display/msm/qcom,sm6150-mdss.yaml >> +++ b/Documentation/devicetree/bindings/display/msm/qcom,sm6150-mdss.yaml >> @@ -51,6 +51,16 @@ patternProperties: >> compatible: >> const: qcom,sm6150-dpu >> >> + "^displayport-controller@[0-9a-f]+$": >> + type: object >> + additionalProperties: true >> + properties: >> + compatible: >> + items: >> + - const: qcom,sm6150-dp >> + - const: qcom,sm8150-dp > Perhaps I'm missing something, but if sm6150-dp is the same controller > as sm8150-dp, which is the same controller as sm8350-dp...doesn't that > imply that sm6150-dp is the same as sm8350-dp and we could not mention > the sm8150-dp here? > > Regards, > Bjorn
I have discussed this with Dmitry in message-id <20250916-add-dp-controller-support-for-sm6150-v3-1-dd60ebbd1...@oss.qualcomm.com> SM6150 uses the same controller IP as SM8150 and should fall back to sm8350 for consistency. And when running CHECK_DTBS, I encountered DTS compatible warnings, which is why all three compatibles are listed. >> + - const: qcom,sm8350-dp >> + >> "^dsi@[0-9a-f]+$": >> type: object >> additionalProperties: true >> >> -- >> 2.34.1 >> >>
