Reviewing several patchsets for newer platforms made me understand 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.
Changes since v2:
- Moved status property to the last place for msm8998, sdm845 (Konrad)
Changes since v1:
- Split large patchset into smaller parts
- Rebased on phy/next
Dmitry Baryshkov (11):
dt-bindings: phy: migrate QMP UFS PHY bindings to
qcom,sc8280xp-qmp-ufs-phy.yaml
phy: qcom-qmp-ufs: populate offsets configuration
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
.../phy/qcom,msm8996-qmp-ufs-phy.yaml | 244 ------------------
.../phy/qcom,sc8280xp-qmp-ufs-phy.yaml | 48 +++-
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 +-
drivers/phy/qualcomm/phy-qcom-qmp-ufs.c | 10 +
12 files changed, 114 insertions(+), 381 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/phy/qcom,msm8996-qmp-ufs-phy.yaml
--
2.39.2
