From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH 09/14] arm64: dts: qcom: sc8180x: rename labels for DSI nodes
Date: Wed, 31 May 2023 04:16:18 +0300 [thread overview]
Message-ID: <20230531011623.3808538-10-dmitry.baryshkov@linaro.org> (raw)
In-Reply-To: <20230531011623.3808538-1-dmitry.baryshkov@linaro.org>
Currently in board files MDSS and DSI nodes stay apart, because labels
for DSI nodes do not have the mdss_ prefix. It was found that grouping
all display-related notes is more useful.
To keep all display-related nodes close in the board files, change DSI
node labels from dsi_* to mdss_dsi_*.
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
arch/arm64/boot/dts/qcom/sc8180x.dtsi | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/sc8180x.dtsi b/arch/arm64/boot/dts/qcom/sc8180x.dtsi
index e8613a00fcab..ef970c3479ca 100644
--- a/arch/arm64/boot/dts/qcom/sc8180x.dtsi
+++ b/arch/arm64/boot/dts/qcom/sc8180x.dtsi
@@ -2732,14 +2732,14 @@ dpu_intf0_out: endpoint {
port@1 {
reg = <1>;
dpu_intf1_out: endpoint {
- remote-endpoint = <&dsi0_in>;
+ remote-endpoint = <&mdss_dsi0_in>;
};
};
port@2 {
reg = <2>;
dpu_intf2_out: endpoint {
- remote-endpoint = <&dsi1_in>;
+ remote-endpoint = <&mdss_dsi1_in>;
};
};
@@ -2783,7 +2783,7 @@ opp-460000000 {
};
};
- dsi0: dsi@ae94000 {
+ mdss_dsi0: dsi@ae94000 {
compatible = "qcom,mdss-dsi-ctrl";
reg = <0 0x0ae94000 0 0x400>;
reg-names = "dsi_ctrl";
@@ -2807,7 +2807,7 @@ dsi0: dsi@ae94000 {
operating-points-v2 = <&dsi_opp_table>;
power-domains = <&rpmhpd SC8180X_MMCX>;
- phys = <&dsi0_phy>;
+ phys = <&mdss_dsi0_phy>;
phy-names = "dsi";
status = "disabled";
@@ -2818,14 +2818,14 @@ ports {
port@0 {
reg = <0>;
- dsi0_in: endpoint {
+ mdss_dsi0_in: endpoint {
remote-endpoint = <&dpu_intf1_out>;
};
};
port@1 {
reg = <1>;
- dsi0_out: endpoint {
+ mdss_dsi0_out: endpoint {
};
};
};
@@ -2850,7 +2850,7 @@ opp-358000000 {
};
};
- dsi0_phy: dsi-phy@ae94400 {
+ mdss_dsi0_phy: dsi-phy@ae94400 {
compatible = "qcom,dsi-phy-7nm";
reg = <0 0x0ae94400 0 0x200>,
<0 0x0ae94600 0 0x280>,
@@ -2869,7 +2869,7 @@ dsi0_phy: dsi-phy@ae94400 {
status = "disabled";
};
- dsi1: dsi@ae96000 {
+ mdss_dsi1: dsi@ae96000 {
compatible = "qcom,mdss-dsi-ctrl";
reg = <0 0x0ae96000 0 0x400>;
reg-names = "dsi_ctrl";
@@ -2893,7 +2893,7 @@ dsi1: dsi@ae96000 {
operating-points-v2 = <&dsi_opp_table>;
power-domains = <&rpmhpd SC8180X_MMCX>;
- phys = <&dsi1_phy>;
+ phys = <&mdss_dsi1_phy>;
phy-names = "dsi";
status = "disabled";
@@ -2904,20 +2904,20 @@ ports {
port@0 {
reg = <0>;
- dsi1_in: endpoint {
+ mdss_dsi1_in: endpoint {
remote-endpoint = <&dpu_intf2_out>;
};
};
port@1 {
reg = <1>;
- dsi1_out: endpoint {
+ mdss_dsi1_out: endpoint {
};
};
};
};
- dsi1_phy: dsi-phy@ae96400 {
+ mdss_dsi1_phy: dsi-phy@ae96400 {
compatible = "qcom,dsi-phy-7nm";
reg = <0 0x0ae96400 0 0x200>,
<0 0x0ae96600 0 0x280>,
--
2.39.2
next prev parent reply other threads:[~2023-05-31 1:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 1:16 [PATCH 00/14] arm/arm64: dts: qcom: MDSS nodes cleanup Dmitry Baryshkov
2023-05-31 1:16 ` [PATCH 01/14] arm64: dts: qcom: sc7280: Don't disable MDP explicitly Dmitry Baryshkov
2023-05-31 9:38 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 02/14] arm64: dts: qcom: sm8350-hdk: remove useless enablement of mdss_mdp Dmitry Baryshkov
2023-05-31 9:38 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 03/14] arm64: dts: qcom: sm8450-hdk: " Dmitry Baryshkov
2023-05-31 9:38 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 04/14] arm64: dts: qcom: qrb5165-rb5: " Dmitry Baryshkov
2023-05-31 9:39 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 05/14] arm64: dts: qcom: msm8953: rename labels for DSI nodes Dmitry Baryshkov
2023-05-31 9:40 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 06/14] arm64: dts: qcom: msm8996: " Dmitry Baryshkov
2023-05-31 9:41 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 07/14] arm64: dts: qcom: sc7180: " Dmitry Baryshkov
2023-05-31 9:42 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 08/14] arm64: dts: qcom: sc7280: " Dmitry Baryshkov
2023-05-31 9:42 ` Konrad Dybcio
2023-05-31 1:16 ` Dmitry Baryshkov [this message]
2023-05-31 9:43 ` [PATCH 09/14] arm64: dts: qcom: sc8180x: " Konrad Dybcio
2023-05-31 1:16 ` [PATCH 10/14] arm64: dts: qcom: sdm630: " Dmitry Baryshkov
2023-05-31 9:43 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 11/14] arm64: dts: qcom: sdm845: " Dmitry Baryshkov
2023-05-31 9:44 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 12/14] arm64: dts: qcom: sm8250: " Dmitry Baryshkov
2023-05-31 9:45 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 13/14] arm64: dts: qcom: msm8996: rename labels for HDMI nodes Dmitry Baryshkov
2023-05-31 9:45 ` Konrad Dybcio
2023-05-31 1:16 ` [PATCH 14/14] ARM: dts: qcom: msm8974: rename labels for DSI nodes Dmitry Baryshkov
2023-05-31 9:46 ` Konrad Dybcio
2023-06-13 23:48 ` (subset) [PATCH 00/14] arm/arm64: dts: qcom: MDSS nodes cleanup Bjorn Andersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230531011623.3808538-10-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).