From: Vishnu Santhosh <vishnu.santhosh@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@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: Wed, 21 Oct 2026 10:46:23 +0530 [thread overview]
Message-ID: <6890be00-889f-4dc8-b532-bbbc1f55c844@oss.qualcomm.com> (raw)
In-Reply-To: <40657da7-b823-403b-a5d1-ae384db7f3a8@oss.qualcomm.com>
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.
>
>> + apps_smsm: apps@0 {
>> + reg = <0>;
>> + #qcom,smem-state-cells = <1>;
>> + };
>> + modem_smsm: modem@1 {
>> + reg = <1>;
>> + interrupts = <GIC_SPI 69 IRQ_TYPE_EDGE_RISING 0>;
>> + interrupt-controller;
>> + #interrupt-cells = <2>;
>> + };
> Please retain a newline between each subnode and between the last property
> and the first subnode
ok. I will fix in next revision.
>
>> + };
>> +
>> soc: soc@0 {
>> compatible = "simple-bus";
>>
>> @@ -1866,6 +1891,20 @@ glink-edge {
>> qcom,remote-pid = <1>;
>> label = "mpss";
>> };
>> +
>> + bam_dmux: bam-dmux {
> Nodes should be sorted within their scope
ok. I will fix in next revision.
>
>> + compatible = "qcom,bam-dmux";
>> + interrupt-parent = <&modem_smsm>;
>> + interrupts = <1 IRQ_TYPE_EDGE_BOTH>,
>> + <11 IRQ_TYPE_EDGE_BOTH>;
> interrupts-extended = <&foo bar baz>
ok. I will fix in next revision.
>> + interrupt-names = "pc", "pc-ack";
>> + qcom,smem-states = <&apps_smsm 1>, <&apps_smsm 11>;
>> + qcom,smem-state-names = "pc", "pc-ack";
> 1 entry a line, please
>
> [...]
ok. I will fix in next revision.
>
>> base-commit: 518e5b794c06c0f0eb40df3e202274a66202c137
>> change-id: 20260603-qcom-shikra-dts-bam-dmux-7fdcbb6fb662
>> prerequisite-message-id: 20260908-shikra-pas-bam-dmux-binding-v4-1-6044889e7e3d@oss.qualcomm.com
>> prerequisite-patch-id: c3d19e8dbf9451f9f8155c86c21a4e6b5dc796d0
>> prerequisite-message-id: 20260920-qcom-bam-dma-vmid-ext-v2-1-4dbbff0e57c8@oss.qualcomm.com
>> prerequisite-patch-id: 30840b157a197cc896556c0152b26a00abba0010
>> prerequisite-message-id: 20260920-qcom-bam-dmux-vmid-ext-v2-0-ef5ca2178378@oss.qualcomm.com
>> prerequisite-patch-id: a9c2ce26fabf293f94f384409991f8a9b3afaafa
>> prerequisite-patch-id: c4d2876bea87e825468eb3bd116bfdf5a203f7c1
> This list screams ""can't merge this patch"". Please either send changes
> in a series or hold off until the dependencies are met.
>
> Konrad
Understood.
Vishnu
prev parent reply other threads:[~2026-10-21 5:16 UTC|newest]
Thread overview: 3+ 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 [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=6890be00-889f-4dc8-b532-bbbc1f55c844@oss.qualcomm.com \
--to=vishnu.santhosh@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=deepak.singh@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@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=robh@kernel.org \
--cc=stephan@gerhold.net \
/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®