| Message ID | 20221125123638.823261-17-bryan.odonoghue@linaro.org (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | mdss-dsi-ctrl binding and dts fixes | expand |
On 25/11/2022 14:36, Bryan O'Donoghue wrote: > Add silicon specific compatible qcom,sdm660-dsi-ctrl to the > mdss-dsi-ctrl block. This allows us to differentiate the specific bindings > for sdm660 against the yaml documentation. > > Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> > --- > arch/arm64/boot/dts/qcom/sdm660.dtsi | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/arch/arm64/boot/dts/qcom/sdm660.dtsi b/arch/arm64/boot/dts/qcom/sdm660.dtsi > index 10bf1c45cf6ec..f8ec728e67f3d 100644 > --- a/arch/arm64/boot/dts/qcom/sdm660.dtsi > +++ b/arch/arm64/boot/dts/qcom/sdm660.dtsi > @@ -154,7 +154,8 @@ mdp5_intf2_out: endpoint { > > &mdss { > dsi1: dsi@c996000 { > - compatible = "qcom,mdss-dsi-ctrl"; > + compatible = "qcom,sdm660-dsi-ctrl", > + "qcom,mdss-dsi-ctrl"; So, we'd end up with two identical DSI hosts, but one has compatible 'qcom,sdm660-dsi-ctrl' and another one 'qcom,sdm630-dsi-ctrl'. I think, use sdm660 for both of them (for both sdm630 and sdm660) > reg = <0x0c996000 0x400>; > reg-names = "dsi_ctrl"; >
diff --git a/arch/arm64/boot/dts/qcom/sdm660.dtsi b/arch/arm64/boot/dts/qcom/sdm660.dtsi index 10bf1c45cf6ec..f8ec728e67f3d 100644 --- a/arch/arm64/boot/dts/qcom/sdm660.dtsi +++ b/arch/arm64/boot/dts/qcom/sdm660.dtsi @@ -154,7 +154,8 @@ mdp5_intf2_out: endpoint { &mdss { dsi1: dsi@c996000 { - compatible = "qcom,mdss-dsi-ctrl"; + compatible = "qcom,sdm660-dsi-ctrl", + "qcom,mdss-dsi-ctrl"; reg = <0x0c996000 0x400>; reg-names = "dsi_ctrl";
Add silicon specific compatible qcom,sdm660-dsi-ctrl to the mdss-dsi-ctrl block. This allows us to differentiate the specific bindings for sdm660 against the yaml documentation. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> --- arch/arm64/boot/dts/qcom/sdm660.dtsi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)