From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Gopikrishna Garmidi <gopikrishna.garmidi@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>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>,
Pankaj Patil <pankaj.patil@oss.qualcomm.com>
Cc: Rajendra Nayak <rajendra.nayak@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] arm64: dts: qcom: Add Kalambo SoC
Date: Mon, 20 Jul 2026 17:41:19 +0200 [thread overview]
Message-ID: <7bcdd18d-a001-41c7-91bb-3b182859970b@oss.qualcomm.com> (raw)
In-Reply-To: <782d626c-2545-4719-9833-efbc9ba82871@oss.qualcomm.com>
On 7/20/26 5:04 PM, Gopikrishna Garmidi wrote:
>
> Hi Konrad,
>
> Thanks a lot for the review and for catching these
>> On 7/18/26 2:06 PM, Gopikrishna Garmidi wrote:
>>> Introduce support for the Qualcomm Kalambo SoC. It is derived from Mahua
>>> with CPU cluster 0 removed, leaving it with just cluster 1. As a result,
>>> the PDP mailbox and SCP low-priority register windows are updated to
>>> match the reduced CPU complex. Everything else should work as-is.
[...]
> Does this look right to you, or would you prefer re-pointing cluster0's cores in place rather than delete + re-add?
Let's just delete the whole map and re-define it, I think
that's the least painful way to do it
>
>>
>> [...]
>>
>>> +&pdp0_mbox {
>>> + reg = <0 0x17610000 0 0x8000>, <0 0x1a980000 0 0x8000>;
>>> +};
>>
>> Are you sure about this change?
>
> Yes — confirmed against the SoC memory map. The Tx window is the NCC0/NCC1 mailbox instance; dropping the former cluster0 moves the Tx base from NCC0 (0x19980000) to NCC1 (0x1a980000), while reg[0] (Rx) is shared and unchanged. I'll note this in the commit message.
Got it, I overlooked the 0/1 difference in the register name when
comparing
Konrad
next prev parent reply other threads:[~2026-07-20 15:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 12:06 [PATCH 0/5] arm64: dts: qcom: Add Kalambo SoC and CRD Gopikrishna Garmidi
2026-07-18 12:06 ` [PATCH 1/5] dt-bindings: arm: qcom: Document Kalambo SoC and board Gopikrishna Garmidi
2026-07-18 12:13 ` sashiko-bot
2026-07-18 12:06 ` [PATCH 2/5] arm64: dts: qcom: Add Kalambo SoC Gopikrishna Garmidi
2026-07-18 12:17 ` sashiko-bot
2026-07-20 8:57 ` Konrad Dybcio
2026-07-20 15:04 ` Gopikrishna Garmidi
2026-07-20 15:41 ` Konrad Dybcio [this message]
2026-07-20 21:57 ` Dmitry Baryshkov
2026-07-18 12:06 ` [PATCH 3/5] arm64: dts: qcom: Add Kalambo CRD Gopikrishna Garmidi
2026-07-18 12:16 ` sashiko-bot
2026-07-20 8:58 ` Konrad Dybcio
2026-07-18 12:06 ` [PATCH 4/5] firmware: qcom: scm: Allow QSEECOM on " Gopikrishna Garmidi
2026-07-18 12:15 ` sashiko-bot
2026-07-20 8:52 ` Konrad Dybcio
2026-07-20 21:58 ` Dmitry Baryshkov
2026-07-18 12:06 ` [PATCH 5/5] soc: qcom: ubwc: Add Kalambo UBWC config Gopikrishna Garmidi
2026-07-20 8:52 ` Konrad Dybcio
2026-07-20 21:59 ` 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=7bcdd18d-a001-41c7-91bb-3b182859970b@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gopikrishna.garmidi@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.patil@oss.qualcomm.com \
--cc=rajendra.nayak@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sibi.sankar@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