From: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Georgi Djakov <djakov@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>
Subject: Re: [PATCH v3 08/10] arm64: dts: qcom: shikra: Enable CDSP, LPAICP and MPSS on EVK boards
Date: Mon, 8 Jun 2026 18:24:59 +0530 [thread overview]
Message-ID: <18325758-eb01-4b2c-9e9b-b06252f50b73@oss.qualcomm.com> (raw)
In-Reply-To: <ykcbo7dkl2rrjdzutpwsc3wmnub5r7h3zuspxiyh5v432whb65@sbaar24glpta>
On 6/6/2026 6:02 PM, Dmitry Baryshkov wrote:
> On Mon, Jun 01, 2026 at 06:25:10PM +0530, Komal Bajaj wrote:
>> From: Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>
>>
>> Enable CDSP, LPAICP and MPSS for Qualcomm's Shikra CQM, CQS and
>> IQS EVK board.
>>
>> Signed-off-by: Bibek Kumar Patro <bibek.patro@oss.qualcomm.com>
>> Signed-off-by: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts | 19 +++++++++++++++++++
>> arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts | 19 +++++++++++++++++++
>> arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts | 19 +++++++++++++++++++
>> 3 files changed, 57 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts b/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
>> index 0a52ab9b7a4c..b112b21b1d79 100644
>> --- a/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
>> +++ b/arch/arm64/boot/dts/qcom/shikra-cqm-evk.dts
>> @@ -23,6 +23,25 @@ chosen {
>> };
>> };
>>
>> +&remoteproc_cdsp {
>> + firmware-name = "qcom/shikra/cdsp.mbn";
>> +
>> + status = "okay";
>> +};
>> +
>> +&remoteproc_lpaicp {
>> + firmware-name = "qcom/shikra/lpaicp.mbn",
>> + "qcom/shikra/lpaicp_dtb.mbn";
>> +
>> + status = "okay";
>> +};
>> +
>> +&remoteproc_mpss {
>> + firmware-name = "qcom/shikra/cqm/qdsp6sw.mbn";
> qcom/shikra/qdsp6sw.mbn
>
>> +
>> + status = "okay";
>> +};
>> +
>> &sdhc_1 {
>> vmmc-supply = <&pm4125_l20>;
>> vqmmc-supply = <&pm4125_l14>;
>> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts b/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
>> index b3f19a64d7ae..e62ba5aef71f 100644
>> --- a/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
>> +++ b/arch/arm64/boot/dts/qcom/shikra-cqs-evk.dts
>> @@ -23,6 +23,25 @@ chosen {
>> };
>> };
>>
>> +&remoteproc_cdsp {
>> + firmware-name = "qcom/shikra/cdsp.mbn";
>> +
>> + status = "okay";
>> +};
>> +
>> +&remoteproc_lpaicp {
>> + firmware-name = "qcom/shikra/lpaicp.mbn",
>> + "qcom/shikra/lpaicp_dtb.mbn";
>> +
>> + status = "okay";
>> +};
>> +
>> +&remoteproc_mpss {
>> + firmware-name = "qcom/shikra/cqs/qdsp6sw.mbn";
> qcom/shikra/qdsp6sw_nm.mbn
We cannot change the firmware name, as our vendor builds and internal
tooling depend on the same naming convention for all three Shikra
variants. This is also why the binaries are placed under different paths.
Thanks
Komal
>
>> +
>> + status = "okay";
>> +};
>> +
>> &sdhc_1 {
>> vmmc-supply = <&pm4125_l20>;
>> vqmmc-supply = <&pm4125_l14>;
>> diff --git a/arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts b/arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
>> index 3003a47bd759..727809430fd1 100644
>> --- a/arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
>> +++ b/arch/arm64/boot/dts/qcom/shikra-iqs-evk.dts
>> @@ -23,6 +23,25 @@ chosen {
>> };
>> };
>>
>> +&remoteproc_cdsp {
>> + firmware-name = "qcom/shikra/cdsp.mbn";
>> +
>> + status = "okay";
>> +};
>> +
>> +&remoteproc_lpaicp {
>> + firmware-name = "qcom/shikra/lpaicp.mbn",
>> + "qcom/shikra/lpaicp_dtb.mbn";
>> +
>> + status = "okay";
>> +};
>> +
>> +&remoteproc_mpss {
>> + firmware-name = "qcom/shikra/cqs/qdsp6sw.mbn";
> qcom/shikra/qdsp6sw_nm.mbn
>
>> +
>> + status = "okay";
>> +};
>> +
>> &sdhc_1 {
>> vmmc-supply = <&pm8150_l17>;
>> vqmmc-supply = <&pm8150_s4>;
>>
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2026-06-08 12:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 12:55 [PATCH v3 00/10] arm64: dts: qcom: Extend Shikra device tree with peripheral and subsystem support Komal Bajaj
2026-06-01 12:55 ` [PATCH v3 01/10] dt-bindings: dma: qcom,gpi: Document GPI DMA engine for Shikra SoC Komal Bajaj
2026-06-05 12:11 ` Krzysztof Kozlowski
2026-06-01 12:55 ` [PATCH v3 02/10] dt-bindings: interconnect: qcom-bwmon: Add Shikra cpu-bwmon compatible Komal Bajaj
2026-06-05 12:12 ` Krzysztof Kozlowski
2026-06-01 12:55 ` [PATCH v3 03/10] arm64: dts: qcom: Add QUPv3 configuration for Shikra Komal Bajaj
2026-06-06 12:46 ` Dmitry Baryshkov
2026-06-01 12:55 ` [PATCH v3 04/10] arm64: dts: qcom: shikra: Add DDR BWMON support Komal Bajaj
2026-06-01 12:55 ` [PATCH v3 05/10] arm64: dts: qcom: shikra: Add cpufreq-hw, EPSS L3 interconnect and OPP tables Komal Bajaj
2026-06-01 12:55 ` [PATCH v3 06/10] arm64: dts: qcom: shikra: Add SMP2P nodes Komal Bajaj
2026-06-06 12:45 ` Dmitry Baryshkov
2026-06-01 12:55 ` [PATCH v3 07/10] arm64: dts: qcom: shikra: Add CDSP, LPAICP, MPSS remoteproc PAS nodes Komal Bajaj
2026-06-01 12:55 ` [PATCH v3 08/10] arm64: dts: qcom: shikra: Enable CDSP, LPAICP and MPSS on EVK boards Komal Bajaj
2026-06-06 12:32 ` Dmitry Baryshkov
2026-06-08 12:54 ` Komal Bajaj [this message]
2026-06-01 12:55 ` [PATCH v3 09/10] arm64: dts: qcom: shikra: Enable TSENS and thermal zones Komal Bajaj
2026-06-06 12:41 ` Dmitry Baryshkov
2026-06-01 12:55 ` [PATCH v3 10/10] arm64: dts: qcom: shikra: Enable Bluetooth and WiFi on EVK boards Komal Bajaj
2026-06-06 12:45 ` Dmitry Baryshkov
2026-06-08 13:00 ` Komal Bajaj
2026-06-06 12:57 ` Loic Poulain
2026-06-08 2:26 ` Miaoqing Pan
2026-06-08 8:22 ` Loic Poulain
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=18325758-eb01-4b2c-9e9b-b06252f50b73@oss.qualcomm.com \
--to=komal.bajaj@oss.qualcomm.com \
--cc=Frank.Li@kernel.org \
--cc=andersson@kernel.org \
--cc=bibek.patro@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=djakov@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=robh@kernel.org \
--cc=vkoul@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