Devicetree
 help / color / mirror / Atom feed
From: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Abel Vesa <abelvesa@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,
	Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Subject: [PATCH 0/4] arm64: dts: qcom: Introduce Qualcomm Hawi platform device tree
Date: Wed, 23 Sep 2026 01:48:34 +0530	[thread overview]
Message-ID: <20260923-hawi-dt-post-v1-0-e41473b6298b@oss.qualcomm.com> (raw)

Introduce the Device Tree for the recently announced[1] Snapdragon SoC
from Qualcomm: Hawi

[1]
https://www.qualcomm.com/smartphones/products/8-series/snapdragon-8-elite-extreme-gen-6-mobile-platform

Series contains patches covering Oryon new CPU variants binding, IPCC header
and base Device Tree for the Hawi SoC, MTP (Mobile Test Platform).

Features added and enabled:

- CPUs with PSCI idle states and cpufreq
- Interrupt-controller with PDC wakeup support
- Timers, TCSR Clock Controllers
- Reserved Shared memory
- GCC/RPMHCC/VIDEOCC/GPUCC/CAMCC
- TLMM
- Interconnect with CPU BWMONs
- QuP with UART
- SMMUs
- RPMHPD and regulator
- UFS with inline crypto engine (ICE)
- LLCC
- Watchdog
- CDSP, ADSP with SMP2P, Fastrpc
- BUS with I2C and SPI
- USB2/USB3/type-C
- Modem and SoCCP
- SDHCI
- random number generator (RNG)
- TSENS
- PCIe

Series dependency:

- Series is based on next-20260921
- USB binding : https://lore.kernel.org/lkml/20260811160835.2968717-1-mojha@qti.qualcomm.com/   (Reviewed)
- CDSP driver data and its binding: https://lore.kernel.org/all/20260914084312.3812408-1-mukesh.ojha@oss.qualcomm.com/   (Reviewed)
- For Modem binding - https://lore.kernel.org/lkml/20260805132129.2713174-2-mukesh.ojha@oss.qualcomm.com/     (Reviewed)
- Boot up dependency : https://lore.kernel.org/all/20260911-rsc_read-v2-1-98675c248278@oss.qualcomm.com/  (In Review)

To: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzk+dt@kernel.org>
To: Conor Dooley <conor+dt@kernel.org>
To: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>
To: Abel Vesa <abelvesa@kernel.org>
Cc: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-arm-msm@vger.kernel.org

Signed-off-by: Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
---
Mukesh Ojha (4):
      dt-bindings: arm: cpus: Add Oryon PartNum 3 CPU compatibles
      arm64: dts: qcom: hawi: Add header file for IPCC physical client IDs
      arm64: dts: qcom: Introduce Hawi SoC
      arm64: dts: qcom: hawi: Add base MTP board

 Documentation/devicetree/bindings/arm/cpus.yaml |    3 +
 arch/arm64/boot/dts/qcom/Makefile               |    1 +
 arch/arm64/boot/dts/qcom/hawi-ipcc.h            |   61 +
 arch/arm64/boot/dts/qcom/hawi-mtp.dts           | 1000 ++++
 arch/arm64/boot/dts/qcom/hawi.dtsi              | 6847 +++++++++++++++++++++++
 arch/arm64/boot/dts/qcom/pmh0104-hawi.dtsi      |  103 +
 6 files changed, 8015 insertions(+)
---
base-commit: 5c4d4169604b335c38bbc79bc1fc03042981fc6f
change-id: 20260922-hawi-dt-post-a1c9f4d03e8b
prerequisite-change-id: 20260910-rsc_read-27d689e37cb5:v2
prerequisite-patch-id: 76c7708564fe28e2b9bfa7037fede190059efdcd
prerequisite-patch-id: abfa9de0466722476fdd75d14ec75a362d6dbd27
prerequisite-message-id: <20260805132129.2713174-1-mukesh.ojha@oss.qualcomm.com>
prerequisite-patch-id: 8e93d1f80fb9570d7e77b9a1bed4c66957a9584b
prerequisite-patch-id: 3247ca257cbfefdd381431b6cc957ac1de9535c2
prerequisite-patch-id: d0da917632a377ad57777719217a3a833885e316
prerequisite-message-id: <20260914084312.3812408-1-mukesh.ojha@oss.qualcomm.com>
prerequisite-patch-id: ccb139f7eee9b87fb8d03720b846a01534960fe2
prerequisite-patch-id: b62a4d66221428ef7a141a9b3ff38fb087d6a092
prerequisite-message-id: <20260811160835.2968717-1-mojha@qti.qualcomm.com>
prerequisite-patch-id: d29faa9849aa39f544b8959a02f1f45e9aeda5e7

Best regards,
--  
-Mukesh Ojha


             reply	other threads:[~2026-09-22 20:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 20:18 Mukesh Ojha [this message]
2026-09-22 20:18 ` [PATCH 1/4] dt-bindings: arm: cpus: Add Oryon PartNum 3 CPU compatibles Mukesh Ojha
2026-09-22 20:18 ` [PATCH 2/4] arm64: dts: qcom: hawi: Add header file for IPCC physical client IDs Mukesh Ojha
2026-09-22 20:18 ` [PATCH 3/4] arm64: dts: qcom: Introduce Hawi SoC Mukesh Ojha
2026-09-22 20:38   ` sashiko-bot
2026-09-23 17:36     ` Mukesh Ojha
2026-09-23 10:41   ` Konrad Dybcio
2026-09-23 13:03     ` Mukesh Ojha
2026-09-22 20:18 ` [PATCH 4/4] arm64: dts: qcom: hawi: Add base MTP board Mukesh Ojha
2026-09-22 20:39   ` sashiko-bot
2026-09-23 13:04     ` Mukesh Ojha
2026-09-23 10:42   ` Konrad Dybcio
2026-09-23 12:59     ` Mukesh Ojha
2026-09-24  1:06 ` (subset) [PATCH 0/4] arm64: dts: qcom: Introduce Qualcomm Hawi platform device tree Bjorn Andersson

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=20260923-hawi-dt-post-v1-0-e41473b6298b@oss.qualcomm.com \
    --to=mukesh.ojha@oss.qualcomm.com \
    --cc=abelvesa@kernel.org \
    --cc=andersson@kernel.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-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=robh@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