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 0/9] arm64: dts: qcom: switch UFS QMP PHY to new style of bindings
Date: Tue, 5 Dec 2023 06:25:43 +0300 [thread overview]
Message-ID: <20231205032552.1583336-1-dmitry.baryshkov@linaro.org> (raw)
This is an unmerged excerpt of the previous series that converted UFS
QMP PHY to newer style of bindings (single registers region instead of
listing each resource separately and having child node for the PHYs).
Changes since v2:
- Rebased on linux-next
- Dropped merged patches
Changes since v1:
- Split large patchset into smaller parts
- Rebased on phy/next
Dmitry Baryshkov (9):
arm64: dts: qcom: msm8996: switch UFS QMP PHY to new style of bindings
arm64: dts: qcom: msm8998: switch UFS QMP PHY to new style of bindings
arm64: dts: qcom: sdm845: switch UFS QMP PHY to new style of bindings
arm64: dts: qcom: sm6115: switch UFS QMP PHY to new style of bindings
arm64: dts: qcom: sm6350: switch UFS QMP PHY to new style of bindings
arm64: dts: qcom: sm8150: switch UFS QMP PHY to new style of bindings
arm64: dts: qcom: sm8250: switch UFS QMP PHY to new style of bindings
arm64: dts: qcom: sm8350: switch UFS QMP PHY to new style of bindings
arm64: dts: qcom: sm8450: switch UFS QMP PHY to new style of bindings
arch/arm64/boot/dts/qcom/msm8996.dtsi | 25 +++++++++---------------
arch/arm64/boot/dts/qcom/msm8998.dtsi | 18 ++++-------------
arch/arm64/boot/dts/qcom/sdm845.dtsi | 19 +++++-------------
arch/arm64/boot/dts/qcom/sm6115.dtsi | 17 +++++-----------
arch/arm64/boot/dts/qcom/sm6350.dtsi | 18 ++++-------------
arch/arm64/boot/dts/qcom/sm8150.dtsi | 20 ++++++-------------
arch/arm64/boot/dts/qcom/sm8250.dtsi | 20 ++++++-------------
arch/arm64/boot/dts/qcom/sm8350.dtsi | 28 ++++++++++-----------------
arch/arm64/boot/dts/qcom/sm8450.dtsi | 28 ++++++++++-----------------
9 files changed, 59 insertions(+), 134 deletions(-)
--
2.39.2
next 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 Dmitry Baryshkov [this message]
2023-12-05 3:25 ` [PATCH v3 1/9] arm64: dts: qcom: msm8996: switch UFS QMP PHY to new style of bindings Dmitry Baryshkov
2023-12-05 3:25 ` [PATCH v3 2/9] arm64: dts: qcom: msm8998: " Dmitry Baryshkov
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-1-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).