Devicetree
 help / color / mirror / Atom feed
From: Aneesh Pradhan <aneeshpradhan2004@gmail.com>
To: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Catherine Frederick <serenity@floorchan.org>,
	linux-clk@vger.kernel.org, Aneesh Pradhan <aneeshpradhan@acm.org>
Subject: [PATCH v2 0/3] arm64: dts: qcom: initial MSM8920 and Motorola Moto E4 (perry)
Date: Wed, 22 Jul 2026 18:46:24 -0700	[thread overview]
Message-ID: <20260723014627.63310-1-aneeshpradhan@acm.org> (raw)
In-Reply-To: <20260723012431.48499-1-aneeshpradhan@acm.org>

Initial upstream support for MSM8920 and the Motorola Moto E4 (perry).

Depends on the separate qcom,rpmcc-msm8920 clk series (binding +
clk-smd-rpm) for the MSM8920 rpmcc compatible used by msm8920.dtsi.

This is a trimmed mainline-first subset of msm89x7-mainline/linux#48,
rewritten so every phandle exists on qcom/for-next's msm8917 / pm8937 /
pmi8950 (the fork DT assumed richer SoC/PMIC nodes that are not
upstream yet).

Included: regulators, eMMC/SD, USB OTG (gpio-id extcon), keys, RMI4
touch + reset-gpios, BMA253 (i2c-gpio), WCNSS (wcn3660b), PMI8950 WLED.
Deferred follow-ups: DSI panel, IPA, QDSP6 audio, FG/smbcharger, modem.

DTB build verified: msm8917-motorola-perry.dtb + msm8920-motorola-perry.dtb.

Changes since v1:
- Sort Makefile DTB entries alphabetically: place
  msm8917-motorola-perry.dtb before msm8917-xiaomi-*, keeping
  msm8920-motorola-perry.dtb after the msm8917 block (Sashiko review
  on v1 patch 3/3).

Catherine Frederick (coolguy) (3):
  dt-bindings: arm: qcom: add MSM8920 and Motorola Moto E4 (perry)
  arm64: dts: qcom: add initial MSM8920 device tree
  arm64: dts: qcom: add initial Motorola Moto E4 (perry) support

 .../devicetree/bindings/arm/qcom.yaml         |   7 +
 arch/arm64/boot/dts/qcom/Makefile             |   2 +
 .../qcom/msm8917-motorola-perry-common.dtsi   | 412 ++++++++++++++++++
 .../boot/dts/qcom/msm8917-motorola-perry.dts  |  20 +
 .../boot/dts/qcom/msm8920-motorola-perry.dts  |  20 +
 arch/arm64/boot/dts/qcom/msm8920.dtsi         |  12 +
 6 files changed, 473 insertions(+)
 create mode 100644 arch/arm64/boot/dts/qcom/msm8917-motorola-perry-common.dtsi
 create mode 100644 arch/arm64/boot/dts/qcom/msm8917-motorola-perry.dts
 create mode 100644 arch/arm64/boot/dts/qcom/msm8920-motorola-perry.dts
 create mode 100644 arch/arm64/boot/dts/qcom/msm8920.dtsi


base-commit: a27464b0b99874d22b04a92186ab7ea9252c3847
-- 
2.53.0


  parent reply	other threads:[~2026-07-23  1:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  1:24 [PATCH 0/2] clk: qcom: add MSM8920 RPM clock controller support Aneesh Pradhan
2026-07-23  1:24 ` [PATCH 1/2] dt-bindings: clock: qcom,rpmcc: add MSM8920 Aneesh Pradhan
2026-07-23  1:24 ` [PATCH 2/2] clk: qcom: smd-rpm: add MSM8920 support Aneesh Pradhan
2026-07-23  1:24 ` [PATCH 0/3] arm64: dts: qcom: initial MSM8920 and Motorola Moto E4 (perry) Aneesh Pradhan
2026-07-23  1:24   ` [PATCH 1/3] dt-bindings: arm: qcom: add " Aneesh Pradhan
2026-07-23  1:24   ` [PATCH 2/3] arm64: dts: qcom: add initial MSM8920 device tree Aneesh Pradhan
2026-07-23  1:24   ` [PATCH 3/3] arm64: dts: qcom: add initial Motorola Moto E4 (perry) support Aneesh Pradhan
2026-07-23  1:34     ` sashiko-bot
2026-07-23  1:46   ` Aneesh Pradhan [this message]
2026-07-23  1:46     ` [PATCH v2 1/3] dt-bindings: arm: qcom: add MSM8920 and Motorola Moto E4 (perry) Aneesh Pradhan
2026-07-23  1:46     ` [PATCH v2 2/3] arm64: dts: qcom: add initial MSM8920 device tree Aneesh Pradhan
2026-07-23  1:46     ` [PATCH v2 3/3] arm64: dts: qcom: add initial Motorola Moto E4 (perry) support Aneesh Pradhan
2026-07-23  2:12       ` sashiko-bot

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=20260723014627.63310-1-aneeshpradhan@acm.org \
    --to=aneeshpradhan2004@gmail.com \
    --cc=andersson@kernel.org \
    --cc=aneeshpradhan@acm.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=serenity@floorchan.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