From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Johan Hovold <johan@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org
Subject: [PATCH v2 00/13] phy: qcom-qmp-pcie: convert to newer style of bindings
Date: Mon, 31 Jul 2023 13:57:46 +0300 [thread overview]
Message-ID: <20230731105759.3997549-1-dmitry.baryshkov@linaro.org> (raw)
Reviewing several patchsets for newer platforms made it clear that
having two styles of QMP PHY bindings causes confusion. Despite binding
documents having notes telling that old bindings should be used for
older platforms, it is too easy to attempt adding new platform with
older QMP PHY binding. Thus let's have just a single documented style of
bindings.
Proposed merge strategy: immutable branch with binding and PHY patches,
which can also be merged into Bjorn's dts-for-6.6
Changes since v1:
- Split large patchset into smaller parts
- Rebased on phy/next
Dmitry Baryshkov (13):
dt-bindings: phy: migrate QMP PCIe PHY bindings to
qcom,sc8280xp-qmp-pcie-phy.yaml
phy: qcom-qmp-pcie: simplify clock handling
phy: qcom-qmp-pcie: populate offsets configuration
arm64: dts: qcom: ipq6018: switch PCIe QMP PHY to new style of
bindings
arm64: dts: qcom: ipq8074: switch PCIe QMP PHY to new style of
bindings
arm64: dts: qcom: msm8998: switch PCIe QMP PHY to new style of
bindings
arm64: dts: qcom: sc7280: switch PCIe QMP PHY to new style of bindings
arm64: dts: qcom: sc8180x: switch PCIe QMP PHY to new style of
bindings
arm64: dts: qcom: sdm845: switch PCIe QMP PHY to new style of bindings
arm64: dts: qcom: sm8150: switch PCIe QMP PHY to new style of bindings
arm64: dts: qcom: sm8250: switch PCIe QMP PHY to new style of bindings
arm64: dts: qcom: sm8450: switch PCIe QMP PHY to new style of bindings
ARM: dts: qcom-sdx55: switch PCIe QMP PHY to new style of bindings
.../phy/qcom,ipq8074-qmp-pcie-phy.yaml | 278 +++---------------
.../phy/qcom,msm8998-qmp-pcie-phy.yaml | 97 ++++++
.../phy/qcom,sc8280xp-qmp-pcie-phy.yaml | 34 ++-
arch/arm/boot/dts/qcom/qcom-sdx55.dtsi | 31 +-
arch/arm64/boot/dts/qcom/ipq6018.dtsi | 32 +-
arch/arm64/boot/dts/qcom/ipq8074.dtsi | 63 ++--
arch/arm64/boot/dts/qcom/msm8998.dtsi | 30 +-
arch/arm64/boot/dts/qcom/sc7280.dtsi | 36 +--
arch/arm64/boot/dts/qcom/sc8180x.dtsi | 140 ++++-----
arch/arm64/boot/dts/qcom/sdm845.dtsi | 71 ++---
arch/arm64/boot/dts/qcom/sm8150.dtsi | 70 ++---
arch/arm64/boot/dts/qcom/sm8250.dtsi | 112 +++----
arch/arm64/boot/dts/qcom/sm8450.dtsi | 82 +++---
drivers/phy/qualcomm/phy-qcom-qmp-pcie.c | 162 +++++-----
14 files changed, 520 insertions(+), 718 deletions(-)
create mode 100644 Documentation/devicetree/bindings/phy/qcom,msm8998-qmp-pcie-phy.yaml
--
2.39.2
next reply other threads:[~2023-07-31 10:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 10:57 Dmitry Baryshkov [this message]
2023-07-31 10:57 ` [PATCH v2 01/13] dt-bindings: phy: migrate QMP PCIe PHY bindings to qcom,sc8280xp-qmp-pcie-phy.yaml Dmitry Baryshkov
2023-08-19 13:31 ` Krzysztof Kozlowski
2023-07-31 10:57 ` [PATCH v2 02/13] phy: qcom-qmp-pcie: simplify clock handling Dmitry Baryshkov
2023-07-31 12:56 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 03/13] phy: qcom-qmp-pcie: populate offsets configuration Dmitry Baryshkov
2023-07-31 10:57 ` [PATCH v2 04/13] arm64: dts: qcom: ipq6018: switch PCIe QMP PHY to new style of bindings Dmitry Baryshkov
2023-07-31 19:21 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 05/13] arm64: dts: qcom: ipq8074: " Dmitry Baryshkov
2023-07-31 19:22 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 06/13] arm64: dts: qcom: msm8998: " Dmitry Baryshkov
2023-07-31 19:24 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 07/13] arm64: dts: qcom: sc7280: " Dmitry Baryshkov
2023-07-31 19:25 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 08/13] arm64: dts: qcom: sc8180x: " Dmitry Baryshkov
2023-07-31 19:26 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 09/13] arm64: dts: qcom: sdm845: " Dmitry Baryshkov
2023-07-31 19:26 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 10/13] arm64: dts: qcom: sm8150: " Dmitry Baryshkov
2023-07-31 19:27 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 11/13] arm64: dts: qcom: sm8250: " Dmitry Baryshkov
2023-07-31 19:27 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 12/13] arm64: dts: qcom: sm8450: " Dmitry Baryshkov
2023-07-31 19:28 ` Konrad Dybcio
2023-07-31 10:57 ` [PATCH v2 13/13] ARM: dts: qcom-sdx55: " Dmitry Baryshkov
2023-07-31 19:29 ` Konrad Dybcio
2023-08-17 9:55 ` (subset) [PATCH v2 00/13] phy: qcom-qmp-pcie: convert to newer " Vinod Koul
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=20230731105759.3997549-1-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=johan@kernel.org \
--cc=kishon@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=vkoul@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).