[PATCH v2 0/3] Fix some issues in QCOM UFS bindings

From: Luca Weiss
Date: Fri Dec 30 2022 - 02:44:05 EST


The patches depend on the following patch adding SM6115:
* https://lore.kernel.org/linux-arm-msm/20221030094258.486428-2-iskren.chernev@xxxxxxxxx/

The only remaining validation issues I see in the UFS bindings are solved with
the following patches, but this series doesn't depend on them:
* https://lore.kernel.org/linux-arm-msm/20221228124331.258416-1-krzysztof.kozlowski@xxxxxxxxxx/
* https://lore.kernel.org/linux-arm-msm/20221205100837.29212-2-johan+linaro@xxxxxxxxxx/

To: Andy Gross <agross@xxxxxxxxxx>
To: Bjorn Andersson <andersson@xxxxxxxxxx>
To: Konrad Dybcio <konrad.dybcio@xxxxxxxxxx>
To: Alim Akhtar <alim.akhtar@xxxxxxxxxxx>
To: Avri Altman <avri.altman@xxxxxxx>
To: Bart Van Assche <bvanassche@xxxxxxx>
To: Rob Herring <robh+dt@xxxxxxxxxx>
To: Krzysztof Kozlowski <krzysztof.kozlowski+dt@xxxxxxxxxx>
To: Iskren Chernev <me@xxxxxxxxxxx>
Cc: linux-arm-msm@xxxxxxxxxxxxxxx
Cc: linux-scsi@xxxxxxxxxxxxxxx
Cc: devicetree@xxxxxxxxxxxxxxx
Cc: linux-kernel@xxxxxxxxxxxxxxx
Cc: ~postmarketos/upstreaming@xxxxxxxxxxx
Cc: phone-devel@xxxxxxxxxxxxxxx
Signed-off-by: Luca Weiss <luca.weiss@xxxxxxxxxxxxx>
---
Changes in v2:
- Add new patch adding reg-names to sm6115 & rebase series on top of sm6115
addition
- Fix binding example after sm8450 move, split this patch from original patch
since it became too big
- Move reg-names definition to top-level
- Link to v1: https://lore.kernel.org/r/20221209-dt-binding-ufs-v1-0-8d502f0e18d5@xxxxxxxxxxxxx

---
Luca Weiss (3):
arm64: dts: qcom: sm6115: Add missing reg-names property for UFS
dt-bindings: ufs: qcom: Add reg-names property for ICE
dt-bindings: ufs: qcom: Fix sm8450 bindings

.../devicetree/bindings/ufs/qcom,ufs.yaml | 35 ++++++++++++++++++----
arch/arm64/boot/dts/qcom/sm6115.dtsi | 1 +
2 files changed, 31 insertions(+), 5 deletions(-)
---
base-commit: 98d95cb05f231dd0f155f912ec7823475b112f6e
change-id: 20221209-dt-binding-ufs-2d7f64797ff2

Best regards,
--
Luca Weiss <luca.weiss@xxxxxxxxxxxxx>