From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Vishnu Santhosh <vishnu.santhosh@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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, stephan@gerhold.net,
Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>
Subject: Re: [PATCH v3] arm64: dts: qcom: shikra: Add BAM-DMUX support
Date: Thu, 22 Oct 2026 10:48:27 +0200 [thread overview]
Message-ID: <b27add9e-9398-422e-b7c8-de11afebca4d@oss.qualcomm.com> (raw)
In-Reply-To: <6890be00-889f-4dc8-b532-bbbc1f55c844@oss.qualcomm.com>
On 10/21/26 7:16 AM, Vishnu Santhosh wrote:
>
> On 15-10-2026 02:52 pm, Konrad Dybcio wrote:
>> On 9/20/26 5:28 AM, Vishnu Santhosh wrote:
>>> Add the SMSM state entries, BAM-DMUX node, and BAM DMA controller needed
>>> to provide modem data channels on Shikra.
>>>
>>> Reserve a 256 KiB restricted DMA pool and reference it from both the
>>> BAM-DMUX and BAM DMA nodes. Set qcom,vmid to NAV so the BAM-DMUX driver
>>> can grant the modem access to the complete pool before requesting the DMA
>>> channels.
>> [...]
>>
>>> + smsm {
>>> + compatible = "qcom,smsm";
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> + mboxes = <0>, <&apcs_glb 13>;
>> Why is there a "null" reference?
>
> Each mboxes entry is the outgoing doorbell for the SMSM host with the
> same index. Index 0 is the apps processor itself (apps@0), which has no
> doorbell, so <0> keeps the modem doorbell at index 1. msm8916.dtsi uses
> the same layout.
Got it, thanks
Konrad
prev parent reply other threads:[~2026-10-22 8:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 3:28 Vishnu Santhosh
2026-10-15 9:22 ` Konrad Dybcio
2026-10-21 5:16 ` Vishnu Santhosh
2026-10-22 8:48 ` Konrad Dybcio [this message]
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=b27add9e-9398-422e-b7c8-de11afebca4d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=deepak.singh@oss.qualcomm.com \
--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=robh@kernel.org \
--cc=stephan@gerhold.net \
--cc=vishnu.santhosh@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
all inboxes | Powered by JetHome®