mbox series

[0/6] arm64: dts: qcom: msm8916/39: Clean up labels

Message ID 20230525-msm8916-labels-v1-0-bec0f5fb46fb@gerhold.net (mailing list archive)
Headers show
Series arm64: dts: qcom: msm8916/39: Clean up labels | expand

Message

Stephan Gerhold May 29, 2023, 12:46 p.m. UTC
MSM8916 and MSM8939 are very similar and almost fully "pin-compatible", 
so there are some devices that exist in very similar variants with both 
MSM8916 and MSM8939. To allow sharing definitions for such devices the 
SoCs should be set up as similar as possible, e.g. using the same 
labels. At least for me this will also simplify maintenance and review 
because board DTs do not behave and/or look subtly different.

This series is the first part to clean up some old inconsistencies for 
those SoCs to bring MSM8916 and MSM8939 closer together and also closer 
to newer SoCs. The changes here are very minor and just focused on 
labels. I'll have some more interesting changes (including fixes) later 
but the series would have become too large.

There is no functional changes in any patch of this series.

Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
---
Stephan Gerhold (6):
      arm64: dts: qcom: msm8916: Rename &msmgpio -> &tlmm
      arm64: dts: qcom: msm8916/39: Rename &blsp1_uartN -> &blsp_uartN
      arm64: dts: qcom: msm8916/39: Use consistent name for I2C/SPI pinctrl
      arm64: dts: qcom: msm8916/39: Clean up MDSS labels
      arm64: dts: qcom: pm8916: Rename &wcd_codec -> &pm8916_codec
      arm64: dts: qcom: msm8916: Move aliases to boards

 arch/arm64/boot/dts/qcom/apq8016-sbc.dts           |  72 +--
 arch/arm64/boot/dts/qcom/apq8039-t2.dts            |  30 +-
 arch/arm64/boot/dts/qcom/msm8916-acer-a1-724.dts   |  20 +-
 .../boot/dts/qcom/msm8916-alcatel-idol347.dts      |  30 +-
 arch/arm64/boot/dts/qcom/msm8916-asus-z00l.dts     |  26 +-
 arch/arm64/boot/dts/qcom/msm8916-gplus-fl8005a.dts |  26 +-
 arch/arm64/boot/dts/qcom/msm8916-huawei-g7.dts     |  60 +--
 .../boot/dts/qcom/msm8916-longcheer-l8150.dts      |  26 +-
 .../boot/dts/qcom/msm8916-longcheer-l8910.dts      |  22 +-
 arch/arm64/boot/dts/qcom/msm8916-mtp.dts           |   4 +-
 arch/arm64/boot/dts/qcom/msm8916-pins.dtsi         |  58 +--
 arch/arm64/boot/dts/qcom/msm8916-pm8916.dtsi       |  16 +-
 .../dts/qcom/msm8916-samsung-a2015-common.dtsi     |  56 +-
 .../boot/dts/qcom/msm8916-samsung-a3u-eur.dts      |  18 +-
 .../boot/dts/qcom/msm8916-samsung-a5u-eur.dts      |   6 +-
 .../dts/qcom/msm8916-samsung-e2015-common.dtsi     |   6 +-
 .../boot/dts/qcom/msm8916-samsung-grandmax.dts     |   6 +-
 .../boot/dts/qcom/msm8916-samsung-gt5-common.dtsi  |  20 +-
 arch/arm64/boot/dts/qcom/msm8916-samsung-gt510.dts |  12 +-
 arch/arm64/boot/dts/qcom/msm8916-samsung-gt58.dts  |   8 +-
 .../boot/dts/qcom/msm8916-samsung-j5-common.dtsi   |  22 +-
 .../boot/dts/qcom/msm8916-samsung-serranove.dts    |  48 +-
 arch/arm64/boot/dts/qcom/msm8916-thwc-uf896.dts    |   8 +-
 arch/arm64/boot/dts/qcom/msm8916-thwc-ufi001c.dts  |  10 +-
 arch/arm64/boot/dts/qcom/msm8916-ufi.dtsi          |   9 +-
 .../boot/dts/qcom/msm8916-wingtech-wt88047.dts     |  22 +-
 .../arm64/boot/dts/qcom/msm8916-yiming-uz801v3.dts |   8 +-
 arch/arm64/boot/dts/qcom/msm8916.dtsi              |  95 ++--
 arch/arm64/boot/dts/qcom/msm8939-pm8916.dtsi       |  10 +-
 .../dts/qcom/msm8939-sony-xperia-kanuti-tulip.dts  |   2 +-
 arch/arm64/boot/dts/qcom/msm8939.dtsi              | 570 ++++++++++-----------
 arch/arm64/boot/dts/qcom/pm8916.dtsi               |   2 +-
 32 files changed, 675 insertions(+), 653 deletions(-)
---
base-commit: 048ca08c07e7be8b8df79af2d49a621fc69f7c3b
change-id: 20230525-msm8916-labels-2abf5d4074ce

Best regards,

Comments

Bjorn Andersson May 30, 2023, 12:16 a.m. UTC | #1
On Mon, 29 May 2023 14:46:57 +0200, Stephan Gerhold wrote:
> MSM8916 and MSM8939 are very similar and almost fully "pin-compatible",
> so there are some devices that exist in very similar variants with both
> MSM8916 and MSM8939. To allow sharing definitions for such devices the
> SoCs should be set up as similar as possible, e.g. using the same
> labels. At least for me this will also simplify maintenance and review
> because board DTs do not behave and/or look subtly different.
> 
> [...]

Applied, thanks!

[1/6] arm64: dts: qcom: msm8916: Rename &msmgpio -> &tlmm
      commit: 41e22c2ff38eaea777f1158071539e659aa7980d
[2/6] arm64: dts: qcom: msm8916/39: Rename &blsp1_uartN -> &blsp_uartN
      commit: c310ca82e229124e7b373125d82ea8fdbf2f9f81
[3/6] arm64: dts: qcom: msm8916/39: Use consistent name for I2C/SPI pinctrl
      commit: fdfc21f65023dbbfe11dcd8f106230668ba8d9e5
[4/6] arm64: dts: qcom: msm8916/39: Clean up MDSS labels
      commit: 835f939501769253eb7eb2dc5389b8592a63a3ed
[5/6] arm64: dts: qcom: pm8916: Rename &wcd_codec -> &pm8916_codec
      commit: 274cf2bdd6c94da2bf293f5a6c9a5f712dd4b01e
[6/6] arm64: dts: qcom: msm8916: Move aliases to boards
      commit: 154f23a8d70cd39158cfdcfb71c112f687352da4

Best regards,