Message ID | 20250311122445.3597100-4-quic_amakhija@quicinc.com |
---|---|
State | Superseded |
Headers | show |
Series | Add DSI display support for SA8775P target | expand |
On Tue, Mar 11, 2025 at 05:54:38PM +0530, Ayushi Makhija wrote: > Document DSI controller and phy on SA8775P platform. > > Signed-off-by: Ayushi Makhija <quic_amakhija@quicinc.com> > --- > .../display/msm/qcom,sa8775p-mdss.yaml | 188 ++++++++++++++++++ > 1 file changed, 188 insertions(+) > > diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml > index a90a8b3f1a9e..628ca68871f4 100644 > --- a/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml > +++ b/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml > @@ -52,6 +52,26 @@ patternProperties: > items: > - const: qcom,sa8775p-dp > > + "^dsi@[0-9a-f]+$": > + type: object > + additionalProperties: true > + Drop blank line > + properties: > + compatible: > + items: contains > + - const: qcom,sa8775p-dsi-ctrl > + - const: qcom,mdss-dsi-ctrl Drop fallback Same comments further Best regards, Krzysztof
On 3/12/2025 5:15 PM, Krzysztof Kozlowski wrote: > On Tue, Mar 11, 2025 at 05:54:38PM +0530, Ayushi Makhija wrote: >> Document DSI controller and phy on SA8775P platform. >> >> Signed-off-by: Ayushi Makhija <quic_amakhija@quicinc.com> >> --- >> .../display/msm/qcom,sa8775p-mdss.yaml | 188 ++++++++++++++++++ >> 1 file changed, 188 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml >> index a90a8b3f1a9e..628ca68871f4 100644 >> --- a/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml >> +++ b/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml >> @@ -52,6 +52,26 @@ patternProperties: >> items: >> - const: qcom,sa8775p-dp >> >> + "^dsi@[0-9a-f]+$": >> + type: object >> + additionalProperties: true >> + > > Drop blank line > >> + properties: >> + compatible: >> + items: > > contains > >> + - const: qcom,sa8775p-dsi-ctrl >> + - const: qcom,mdss-dsi-ctrl > > Drop fallback > > Same comments further > > Best regards, > Krzysztof > Hi Krzysztof, Thanks, for the review. Will address the above comments in the next patch. + "^dsi@[0-9a-f]+$": + type: object + additionalProperties: true + properties: + compatible: + contains: + enum: + - qcom,sa8775p-dsi-ctrl + - qcom,mdss-dsi-ctrl + + "^phy@[0-9a-f]+$": + type: object + additionalProperties: true + properties: + compatible: + contains: + enum: + - qcom,sa8775p-dsi-phy-5nm + - qcom,sa8775p-edp-phy Thanks, Ayushi
On 3/12/2025 5:15 PM, Krzysztof Kozlowski wrote: > On Tue, Mar 11, 2025 at 05:54:38PM +0530, Ayushi Makhija wrote: >> Document DSI controller and phy on SA8775P platform. >> >> Signed-off-by: Ayushi Makhija <quic_amakhija@quicinc.com> >> --- >> .../display/msm/qcom,sa8775p-mdss.yaml | 188 ++++++++++++++++++ >> 1 file changed, 188 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml >> index a90a8b3f1a9e..628ca68871f4 100644 >> --- a/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml >> +++ b/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml >> @@ -52,6 +52,26 @@ patternProperties: >> items: >> - const: qcom,sa8775p-dp >> >> + "^dsi@[0-9a-f]+$": >> + type: object >> + additionalProperties: true >> + > > Drop blank line > >> + properties: >> + compatible: >> + items: > > contains > >> + - const: qcom,sa8775p-dsi-ctrl >> + - const: qcom,mdss-dsi-ctrl > > Drop fallback > Hi Krzysztof, I couldn't understand the meaning of "Drop fallback", could please elaborate it ? Thanks, Ayushi
On 08/04/2025 12:38, Ayushi Makhija wrote: >>> + properties: >>> + compatible: >>> + items: >> >> contains >> >>> + - const: qcom,sa8775p-dsi-ctrl >>> + - const: qcom,mdss-dsi-ctrl >> >> Drop fallback >> > > Hi Krzysztof, > > I couldn't understand the meaning of "Drop fallback", could please elaborate it ? Look at SM8750 example on the lists. Keep only front compatible. Best regards, Krzysztof
On Tue, Apr 08, 2025 at 01:03:53PM +0200, Krzysztof Kozlowski wrote: > On 08/04/2025 12:38, Ayushi Makhija wrote: > >>> + properties: > >>> + compatible: > >>> + items: > >> > >> contains > >> > >>> + - const: qcom,sa8775p-dsi-ctrl > >>> + - const: qcom,mdss-dsi-ctrl > >> > >> Drop fallback > >> > > > > Hi Krzysztof, > > > > I couldn't understand the meaning of "Drop fallback", could please elaborate it ? > Look at SM8750 example on the lists. Keep only front compatible. Why?
On 08/04/2025 13:44, Dmitry Baryshkov wrote: > On Tue, Apr 08, 2025 at 01:03:53PM +0200, Krzysztof Kozlowski wrote: >> On 08/04/2025 12:38, Ayushi Makhija wrote: >>>>> + properties: >>>>> + compatible: >>>>> + items: >>>> >>>> contains >>>> >>>>> + - const: qcom,sa8775p-dsi-ctrl >>>>> + - const: qcom,mdss-dsi-ctrl >>>> >>>> Drop fallback >>>> >>> >>> Hi Krzysztof, >>> >>> I couldn't understand the meaning of "Drop fallback", could please elaborate it ? >> Look at SM8750 example on the lists. Keep only front compatible. > > Why? To make things simpler and shorter. Best regards, Krzysztof
On 08/04/2025 21:42, Krzysztof Kozlowski wrote: > On 08/04/2025 13:44, Dmitry Baryshkov wrote: >> On Tue, Apr 08, 2025 at 01:03:53PM +0200, Krzysztof Kozlowski wrote: >>> On 08/04/2025 12:38, Ayushi Makhija wrote: >>>>>> + properties: >>>>>> + compatible: >>>>>> + items: >>>>> >>>>> contains >>>>> >>>>>> + - const: qcom,sa8775p-dsi-ctrl >>>>>> + - const: qcom,mdss-dsi-ctrl >>>>> >>>>> Drop fallback >>>>> >>>> >>>> Hi Krzysztof, >>>> >>>> I couldn't understand the meaning of "Drop fallback", could please elaborate it ? >>> Look at SM8750 example on the lists. Keep only front compatible. >> >> Why? > > To make things simpler and shorter. I'd prefer consistency. Previous platforms use qcom,mdss-dsi-ctrl.
On 08/04/2025 22:26, Dmitry Baryshkov wrote: >>>>>>> + - const: qcom,sa8775p-dsi-ctrl >>>>>>> + - const: qcom,mdss-dsi-ctrl >>>>>> >>>>>> Drop fallback >>>>>> >>>>> >>>>> Hi Krzysztof, >>>>> >>>>> I couldn't understand the meaning of "Drop fallback", could please elaborate it ? >>>> Look at SM8750 example on the lists. Keep only front compatible. >>> >>> Why? >> >> To make things simpler and shorter. > > I'd prefer consistency. Previous platforms use qcom,mdss-dsi-ctrl. Then you should have objected month(s) ago when Rob asked for dropping fallback and since then we consistently drop it. Best regards, Krzysztof
On 09/04/2025 09:07, Krzysztof Kozlowski wrote: > On 08/04/2025 22:26, Dmitry Baryshkov wrote: >>>>>>>> + - const: qcom,sa8775p-dsi-ctrl >>>>>>>> + - const: qcom,mdss-dsi-ctrl >>>>>>> >>>>>>> Drop fallback >>>>>>> >>>>>> >>>>>> Hi Krzysztof, >>>>>> >>>>>> I couldn't understand the meaning of "Drop fallback", could please elaborate it ? >>>>> Look at SM8750 example on the lists. Keep only front compatible. >>>> >>>> Why? >>> >>> To make things simpler and shorter. >> >> I'd prefer consistency. Previous platforms use qcom,mdss-dsi-ctrl. > Then you should have objected month(s) ago when Rob asked for dropping > fallback and since then we consistently drop it. Well... It's still not merged. is it? For SM8750 it kinda makes sense, because the clock handling is different from all other current platforms. For the existing devices... I'm not that sure. > > Best regards, > Krzysztof
On 09/04/2025 17:24, Dmitry Baryshkov wrote: > On 09/04/2025 09:07, Krzysztof Kozlowski wrote: >> On 08/04/2025 22:26, Dmitry Baryshkov wrote: >>>>>>>>> + - const: qcom,sa8775p-dsi-ctrl >>>>>>>>> + - const: qcom,mdss-dsi-ctrl >>>>>>>> >>>>>>>> Drop fallback >>>>>>>> >>>>>>> >>>>>>> Hi Krzysztof, >>>>>>> >>>>>>> I couldn't understand the meaning of "Drop fallback", could please elaborate it ? >>>>>> Look at SM8750 example on the lists. Keep only front compatible. >>>>> >>>>> Why? >>>> >>>> To make things simpler and shorter. >>> >>> I'd prefer consistency. Previous platforms use qcom,mdss-dsi-ctrl. >> Then you should have objected month(s) ago when Rob asked for dropping >> fallback and since then we consistently drop it. > > Well... It's still not merged. is it? > For SM8750 it kinda makes sense, because the clock handling is different > from all other current platforms. For the existing devices... I'm not > that sure. How does it differ? The clock handling does not matter - this is just select of schema for the child node. Best regards, Krzysztof
On Thu, Apr 10, 2025 at 08:08:17AM +0200, Krzysztof Kozlowski wrote: > On 09/04/2025 17:24, Dmitry Baryshkov wrote: > > On 09/04/2025 09:07, Krzysztof Kozlowski wrote: > >> On 08/04/2025 22:26, Dmitry Baryshkov wrote: > >>>>>>>>> + - const: qcom,sa8775p-dsi-ctrl > >>>>>>>>> + - const: qcom,mdss-dsi-ctrl > >>>>>>>> > >>>>>>>> Drop fallback > >>>>>>>> > >>>>>>> > >>>>>>> Hi Krzysztof, > >>>>>>> > >>>>>>> I couldn't understand the meaning of "Drop fallback", could please elaborate it ? > >>>>>> Look at SM8750 example on the lists. Keep only front compatible. > >>>>> > >>>>> Why? > >>>> > >>>> To make things simpler and shorter. > >>> > >>> I'd prefer consistency. Previous platforms use qcom,mdss-dsi-ctrl. > >> Then you should have objected month(s) ago when Rob asked for dropping > >> fallback and since then we consistently drop it. > > > > Well... It's still not merged. is it? > > For SM8750 it kinda makes sense, because the clock handling is different > > from all other current platforms. For the existing devices... I'm not > > that sure. > How does it differ? The clock handling does not matter - this is just > select of schema for the child node. Ah.... I'm sorry, I misinterpreted the email. Yes, having only a single compat here is perfectly fine. Please excuse me for the confusion.
Hi Krzysztof/Dmitry, On 4/10/2025 2:46 PM, Dmitry Baryshkov wrote: > On Thu, Apr 10, 2025 at 08:08:17AM +0200, Krzysztof Kozlowski wrote: >> On 09/04/2025 17:24, Dmitry Baryshkov wrote: >>> On 09/04/2025 09:07, Krzysztof Kozlowski wrote: >>>> On 08/04/2025 22:26, Dmitry Baryshkov wrote: >>>>>>>>>>> + - const: qcom,sa8775p-dsi-ctrl >>>>>>>>>>> + - const: qcom,mdss-dsi-ctrl >>>>>>>>>> >>>>>>>>>> Drop fallback >>>>>>>>>> >>>>>>>>> >>>>>>>>> Hi Krzysztof, >>>>>>>>> >>>>>>>>> I couldn't understand the meaning of "Drop fallback", could please elaborate it ? >>>>>>>> Look at SM8750 example on the lists. Keep only front compatible. >>>>>>> >>>>>>> Why? >>>>>> >>>>>> To make things simpler and shorter. >>>>> >>>>> I'd prefer consistency. Previous platforms use qcom,mdss-dsi-ctrl. >>>> Then you should have objected month(s) ago when Rob asked for dropping >>>> fallback and since then we consistently drop it. >>> >>> Well... It's still not merged. is it? >>> For SM8750 it kinda makes sense, because the clock handling is different >>> from all other current platforms. For the existing devices... I'm not >>> that sure. >> How does it differ? The clock handling does not matter - this is just >> select of schema for the child node. > > Ah.... I'm sorry, I misinterpreted the email. Yes, having only a single > compat here is perfectly fine. Please excuse me for the confusion. > Thanks, for the review. I will write single compatible string. Will update it in next patchset. + "^dsi@[0-9a-f]+$": + type: object + additionalProperties: true + properties: + compatible: + contains: + const: qcom,sa8775p-dsi-ctrl + Thanks, Ayushi
diff --git a/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml b/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml index a90a8b3f1a9e..628ca68871f4 100644 --- a/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml +++ b/Documentation/devicetree/bindings/display/msm/qcom,sa8775p-mdss.yaml @@ -52,6 +52,26 @@ patternProperties: items: - const: qcom,sa8775p-dp + "^dsi@[0-9a-f]+$": + type: object + additionalProperties: true + + properties: + compatible: + items: + - const: qcom,sa8775p-dsi-ctrl + - const: qcom,mdss-dsi-ctrl + + "^phy@[0-9a-f]+$": + type: object + additionalProperties: true + + properties: + compatible: + enum: + - qcom,sa8775p-dsi-phy-5nm + - qcom,sa8775p-edp-phy + required: - compatible @@ -131,6 +151,20 @@ examples: remote-endpoint = <&mdss0_dp0_in>; }; }; + + port@1 { + reg = <1>; + dpu_intf1_out: endpoint { + remote-endpoint = <&mdss0_dsi0_in>; + }; + }; + + port@2 { + reg = <2>; + dpu_intf2_out: endpoint { + remote-endpoint = <&mdss0_dsi1_in>; + }; + }; }; mdss0_mdp_opp_table: opp-table { @@ -158,6 +192,160 @@ examples: }; }; + dsi@ae94000 { + compatible = "qcom,sa8775p-dsi-ctrl", "qcom,mdss-dsi-ctrl"; + reg = <0x0ae94000 0x400>; + reg-names = "dsi_ctrl"; + + interrupt-parent = <&mdss>; + interrupts = <4>; + + clocks = <&dispc_byte_clk>, + <&dispcc_intf_clk>, + <&dispcc_pclk>, + <&dispcc_esc_clk>, + <&dispcc_ahb_clk>, + <&gcc_bus_clk>; + clock-names = "byte", + "byte_intf", + "pixel", + "core", + "iface", + "bus"; + assigned-clocks = <&dispcc_byte_clk>, + <&dispcc_pclk>; + assigned-clock-parents = <&mdss0_dsi0_phy 0>, <&mdss0_dsi0_phy 1>; + phys = <&mdss0_dsi0_phy>; + + operating-points-v2 = <&dsi0_opp_table>; + power-domains = <&rpmhpd SA8775P_MMCX>; + + #address-cells = <1>; + #size-cells = <0>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + mdss0_dsi0_in: endpoint { + remote-endpoint = <&dpu_intf1_out>; + }; + }; + + port@1 { + reg = <1>; + mdss0_dsi0_out: endpoint { }; + }; + }; + + dsi0_opp_table: opp-table { + compatible = "operating-points-v2"; + + opp-358000000 { + opp-hz = /bits/ 64 <358000000>; + required-opps = <&rpmhpd_opp_svs_l1>; + }; + }; + }; + + mdss0_dsi0_phy: phy@ae94400 { + compatible = "qcom,sa8775p-dsi-phy-5nm"; + reg = <0x0ae94400 0x200>, + <0x0ae94600 0x280>, + <0x0ae94900 0x27c>; + reg-names = "dsi_phy", + "dsi_phy_lane", + "dsi_pll"; + + #clock-cells = <1>; + #phy-cells = <0>; + + clocks = <&dispcc_iface_clk>, + <&rpmhcc_ref_clk>; + clock-names = "iface", "ref"; + + vdds-supply = <&vreg_dsi_supply>; + }; + + dsi@ae96000 { + compatible = "qcom,sa8775p-dsi-ctrl", "qcom,mdss-dsi-ctrl"; + reg = <0x0ae96000 0x400>; + reg-names = "dsi_ctrl"; + + interrupt-parent = <&mdss>; + interrupts = <4>; + + clocks = <&dispc_byte_clk>, + <&dispcc_intf_clk>, + <&dispcc_pclk>, + <&dispcc_esc_clk>, + <&dispcc_ahb_clk>, + <&gcc_bus_clk>; + clock-names = "byte", + "byte_intf", + "pixel", + "core", + "iface", + "bus"; + assigned-clocks = <&dispcc_byte_clk>, + <&dispcc_pclk>; + assigned-clock-parents = <&mdss0_dsi1_phy 0>, <&mdss0_dsi1_phy 1>; + phys = <&mdss0_dsi1_phy>; + + operating-points-v2 = <&dsi1_opp_table>; + power-domains = <&rpmhpd SA8775P_MMCX>; + + #address-cells = <1>; + #size-cells = <0>; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + mdss0_dsi1_in: endpoint { + remote-endpoint = <&dpu_intf2_out>; + }; + }; + + port@1 { + reg = <1>; + mdss0_dsi1_out: endpoint { }; + }; + }; + + dsi1_opp_table: opp-table { + compatible = "operating-points-v2"; + + opp-358000000 { + opp-hz = /bits/ 64 <358000000>; + required-opps = <&rpmhpd_opp_svs_l1>; + }; + }; + }; + + mdss0_dsi1_phy: phy@ae96400 { + compatible = "qcom,sa8775p-dsi-phy-5nm"; + reg = <0x0ae96400 0x200>, + <0x0ae96600 0x280>, + <0x0ae96900 0x27c>; + reg-names = "dsi_phy", + "dsi_phy_lane", + "dsi_pll"; + + #clock-cells = <1>; + #phy-cells = <0>; + + clocks = <&dispcc_iface_clk>, + <&rpmhcc_ref_clk>; + clock-names = "iface", "ref"; + + vdds-supply = <&vreg_dsi_supply>; + }; + displayport-controller@af54000 { compatible = "qcom,sa8775p-dp";
Document DSI controller and phy on SA8775P platform. Signed-off-by: Ayushi Makhija <quic_amakhija@quicinc.com> --- .../display/msm/qcom,sa8775p-mdss.yaml | 188 ++++++++++++++++++ 1 file changed, 188 insertions(+)