From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Komal Bajaj <komal.bajaj@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
Ulf Hansson <ulfh@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-mmc@vger.kernel.org,
Imran Shaik <imran.shaik@oss.qualcomm.com>,
Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>,
Monish Chunara <quic_mchunara@quicinc.com>,
Rakesh Kota <rakesh.kota@oss.qualcomm.com>,
Raviteja Laggyshetty <raviteja.laggyshetty@oss.qualcomm.com>,
Sneh Mankad <sneh.mankad@oss.qualcomm.com>,
Vishnu Santhosh <vishnu.santhosh@oss.qualcomm.com>,
Xueyao An <xueyao.an@oss.qualcomm.com>
Subject: Re: [PATCH 2/4] arm64: dts: qcom: Introduce Shikra SoC base dtsi
Date: Fri, 15 May 2026 12:37:26 +0200 [thread overview]
Message-ID: <ced00124-9ba2-49ca-9200-62abd6ac3340@oss.qualcomm.com> (raw)
In-Reply-To: <20260512-shikra-dt-v1-2-716438330dd0@oss.qualcomm.com>
On 5/12/26 6:08 AM, Komal Bajaj wrote:
> Add initial device tree support for the Qualcomm Shikra SoC,
> an IoT-focused platform built around a heterogeneous CPU cluster
> (Cortex-A55 + Cortex-A78C) with RPM-based power and clock management.
[...]
> + pmu {
> + compatible = "arm,armv8-pmuv3";
> + interrupts = <GIC_PPI 5 IRQ_TYPE_LEVEL_HIGH>;
Considering there's 2 core types, you may need something like:
9ce52e908bd5 ("arm64: dts: qcom: sm8650: switch to interrupt-cells 4 to add PPI partitions")
2c06e0797c32 ("arm64: dts: qcom: sm8650: add PPI interrupt partitions for the ARM PMUs")
> + };
> +
> + psci: psci {
Unused label, please drop
otherwise:
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Konrad
next prev parent reply other threads:[~2026-05-15 10:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 4:08 [PATCH 0/4] arm64: dts: qcom: Add initial device tree support for Shikra Komal Bajaj
2026-05-12 4:08 ` [PATCH 1/4] dt-bindings: arm: qcom: Document Shikra and its EVK boards Komal Bajaj
2026-05-15 8:51 ` Krzysztof Kozlowski
2026-05-12 4:08 ` [PATCH 2/4] arm64: dts: qcom: Introduce Shikra SoC base dtsi Komal Bajaj
2026-05-15 10:37 ` Konrad Dybcio [this message]
2026-05-12 4:08 ` [PATCH 3/4] arm64: dts: qcom: Add Shikra CQM SoM platform Komal Bajaj
2026-05-12 4:08 ` [PATCH 4/4] arm64: dts: qcom: Add Shikra CQM and CQS EVK boards Komal Bajaj
2026-05-13 12:04 ` Dmitry Baryshkov
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=ced00124-9ba2-49ca-9200-62abd6ac3340@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=imran.shaik@oss.qualcomm.com \
--cc=komal.bajaj@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krishna.kurapati@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_mchunara@quicinc.com \
--cc=quic_wcheng@quicinc.com \
--cc=rakesh.kota@oss.qualcomm.com \
--cc=raviteja.laggyshetty@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sneh.mankad@oss.qualcomm.com \
--cc=ulfh@kernel.org \
--cc=vishnu.santhosh@oss.qualcomm.com \
--cc=vkoul@kernel.org \
--cc=xueyao.an@oss.qualcomm.com \
/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