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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v3 2/9] arm64: dts: qcom: msm8998: switch UFS QMP PHY to new style of bindings
Date: Tue, 5 Dec 2023 06:25:45 +0300 [thread overview]
Message-ID: <20231205032552.1583336-3-dmitry.baryshkov@linaro.org> (raw)
In-Reply-To: <20231205032552.1583336-1-dmitry.baryshkov@linaro.org>
Change the UFS QMP PHY to use newer style of QMP PHY bindings (single
resource region, no per-PHY subnodes).
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 18 ++++--------------
1 file changed, 4 insertions(+), 14 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi b/arch/arm64/boot/dts/qcom/msm8998.dtsi
index 67a5a0f612d9..5893e52037f3 100644
--- a/arch/arm64/boot/dts/qcom/msm8998.dtsi
+++ b/arch/arm64/boot/dts/qcom/msm8998.dtsi
@@ -1004,7 +1004,7 @@ ufshc: ufshc@1da4000 {
compatible = "qcom,msm8998-ufshc", "qcom,ufshc", "jedec,ufs-2.0";
reg = <0x01da4000 0x2500>;
interrupts = <GIC_SPI 265 IRQ_TYPE_LEVEL_HIGH>;
- phys = <&ufsphy_lanes>;
+ phys = <&ufsphy>;
phy-names = "ufsphy";
lanes-per-direction = <2>;
power-domains = <&gcc UFS_GDSC>;
@@ -1045,11 +1045,7 @@ ufshc: ufshc@1da4000 {
ufsphy: phy@1da7000 {
compatible = "qcom,msm8998-qmp-ufs-phy";
- reg = <0x01da7000 0x18c>;
- #address-cells = <1>;
- #size-cells = <1>;
- status = "disabled";
- ranges;
+ reg = <0x01da7000 0x1000>;
clock-names =
"ref",
@@ -1061,14 +1057,8 @@ ufsphy: phy@1da7000 {
reset-names = "ufsphy";
resets = <&ufshc 0>;
- ufsphy_lanes: phy@1da7400 {
- reg = <0x01da7400 0x128>,
- <0x01da7600 0x1fc>,
- <0x01da7c00 0x1dc>,
- <0x01da7800 0x128>,
- <0x01da7a00 0x1fc>;
- #phy-cells = <0>;
- };
+ #phy-cells = <0>;
+ status = "disabled";
};
tcsr_mutex: hwlock@1f40000 {
--
2.39.2
next prev parent reply other threads:[~2023-12-05 3:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 3:25 [PATCH v3 0/9] arm64: dts: qcom: switch UFS QMP PHY to new style of bindings Dmitry Baryshkov
2023-12-05 3:25 ` [PATCH v3 1/9] arm64: dts: qcom: msm8996: " Dmitry Baryshkov
2023-12-05 3:25 ` Dmitry Baryshkov [this message]
2023-12-05 3:25 ` [PATCH v3 3/9] arm64: dts: qcom: sdm845: " Dmitry Baryshkov
2023-12-05 3:25 ` [PATCH v3 4/9] arm64: dts: qcom: sm6115: " Dmitry Baryshkov
2023-12-05 3:25 ` [PATCH v3 5/9] arm64: dts: qcom: sm6350: " Dmitry Baryshkov
2023-12-05 3:25 ` [PATCH v3 6/9] arm64: dts: qcom: sm8150: " Dmitry Baryshkov
2023-12-05 3:25 ` [PATCH v3 7/9] arm64: dts: qcom: sm8250: " Dmitry Baryshkov
2023-12-05 3:25 ` [PATCH v3 8/9] arm64: dts: qcom: sm8350: " Dmitry Baryshkov
2023-12-05 3:25 ` [PATCH v3 9/9] arm64: dts: qcom: sm8450: " Dmitry Baryshkov
2023-12-17 17:21 ` [PATCH v3 0/9] arm64: dts: qcom: " 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=20231205032552.1583336-3-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@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).