From: Bjorn Andersson <andersson@kernel.org>
To: Vishnu Santhosh <vishnu.santhosh@oss.qualcomm.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kumar Patro <bibek.patro@oss.qualcomm.com>,
Komal Bajaj <komal.bajaj@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>
Subject: Re: [PATCH v3] dt-bindings: remoteproc: qcom,shikra-pas: Allow bam-dmux subnode
Date: Mon, 31 Aug 2026 11:44:21 -0500 [thread overview]
Message-ID: <apWuwq78D8lEBbeA@baldur> (raw)
In-Reply-To: <20260813-shikra-pas-bam-dmux-binding-v3-1-167a3fb50d21@oss.qualcomm.com>
On Thu, Aug 13, 2026 at 04:55:54PM +0530, Vishnu Santhosh wrote:
> Allow an optional bam-dmux subnode under qcom,shikra-mpss-pas by
> referencing qcom,bam-dmux.yaml.
>
This is a statement, not a problem description. From
https://docs.kernel.org/process/submitting-patches.html#describe-your-changes:
"""
Describe your problem. Whether your patch is a one-line bug fix or 5000
lines of a new feature, there must be an underlying problem that
motivated you to do this work. Convince the reviewer that there is a
problem worth fixing and that it makes sense for them to read past the
first paragraph.
"""
> Retarget the example to qcom,shikra-mpss-pas so the new subnode is
> exercised by dt_binding_check.
It's not clear to me why you're changing the existing example. Seems
like a lot of churn.
If you want to use dt_binding_check as a test-case for bam-dmux, perhaps
adding an additional example would allow us to test both cases?
Regards,
Bjorn
>
> Co-developed-by: Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>
> Signed-off-by: Deepak Kumar Singh <deepak.singh@oss.qualcomm.com>
> Signed-off-by: Vishnu Santhosh <vishnu.santhosh@oss.qualcomm.com>
> ---
> Changes in v3:
> - Reword commit message to keep it scoped to the binding change.
> - Retarget the example to qcom,shikra-mpss-pas and add a bam-dmux child.
> - Link to v2: https://lore.kernel.org/r/20260729-shikra-pas-bam-dmux-binding-v2-1-d85fea84c141@oss.qualcomm.com
>
> Changes in v2:
> - Restrict bam-dmux to the qcom,shikra-mpss-pas compatible.
> - Link to v1: https://lore.kernel.org/r/20260727-shikra-pas-bam-dmux-binding-v1-1-c0159c7c3ed4@oss.qualcomm.com
> ---
> .../bindings/remoteproc/qcom,shikra-pas.yaml | 61 ++++++++++++++++------
> 1 file changed, 45 insertions(+), 16 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,shikra-pas.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,shikra-pas.yaml
> index 253b14eb2b598f0ca91854c8ff4d0b785090e621..dd779b595677c0aa58708b4fde725e64d8918434 100644
> --- a/Documentation/devicetree/bindings/remoteproc/qcom,shikra-pas.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/qcom,shikra-pas.yaml
> @@ -44,6 +44,11 @@ properties:
> - description: Firmware name of the Hexagon core
> - description: Firmware name of the Hexagon Devicetree
>
> + bam-dmux:
> + $ref: /schemas/net/qcom,bam-dmux.yaml#
> + description:
> + Qualcomm BAM Data Multiplexer (provides network interface to the modem)
> +
> glink-edge:
> $ref: /schemas/remoteproc/qcom,glink-edge.yaml#
> description:
> @@ -117,6 +122,16 @@ allOf:
> power-domains: false
> power-domain-names: false
>
> + - if:
> + properties:
> + compatible:
> + enum:
> + - qcom,shikra-cdsp-pas
> + - qcom,shikra-lpaicp-pas
> + then:
> + properties:
> + bam-dmux: false
> +
> unevaluatedProperties: false
>
> examples:
> @@ -129,16 +144,16 @@ examples:
> #include <dt-bindings/interrupt-controller/irq.h>
> #include <dt-bindings/power/qcom-rpmpd.h>
>
> - remoteproc@b300000 {
> - compatible = "qcom,shikra-cdsp-pas";
> - reg = <0x0b300000 0x100000>;
> + remoteproc@6080000 {
> + compatible = "qcom,shikra-mpss-pas";
> + reg = <0x06080000 0x100>;
>
> - interrupts-extended = <&intc GIC_SPI 265 IRQ_TYPE_EDGE_RISING>,
> - <&cdsp_smp2p_in 0 IRQ_TYPE_EDGE_RISING>,
> - <&cdsp_smp2p_in 1 IRQ_TYPE_EDGE_RISING>,
> - <&cdsp_smp2p_in 2 IRQ_TYPE_EDGE_RISING>,
> - <&cdsp_smp2p_in 3 IRQ_TYPE_EDGE_RISING>,
> - <&cdsp_smp2p_in 7 IRQ_TYPE_EDGE_RISING>;
> + interrupts-extended = <&intc GIC_SPI 307 IRQ_TYPE_EDGE_RISING>,
> + <&modem_smp2p_in 0 IRQ_TYPE_EDGE_RISING>,
> + <&modem_smp2p_in 1 IRQ_TYPE_EDGE_RISING>,
> + <&modem_smp2p_in 2 IRQ_TYPE_EDGE_RISING>,
> + <&modem_smp2p_in 3 IRQ_TYPE_EDGE_RISING>,
> + <&modem_smp2p_in 7 IRQ_TYPE_EDGE_RISING>;
> interrupt-names = "wdog", "fatal", "ready",
> "handover", "stop-ack", "shutdown-ack";
>
> @@ -151,17 +166,31 @@ examples:
> power-domains = <&rpmpd RPMHPD_CX>;
> power-domain-names = "cx";
>
> - memory-region = <&cdsp_mem>;
> + memory-region = <&mpss_wlan_mem>;
>
> - qcom,smem-states = <&cdsp_smp2p_out 0>;
> + qcom,smem-states = <&modem_smp2p_out 0>;
> qcom,smem-state-names = "stop";
>
> - firmware-name = "qcom/shikra/cdsp.mbn";
> + firmware-name = "qcom/shikra/modem.mbn";
>
> glink-edge {
> - interrupts = <GIC_SPI 261 IRQ_TYPE_EDGE_RISING>;
> - mboxes = <&apcs_glb 4>;
> - qcom,remote-pid = <5>;
> - label = "cdsp";
> + interrupts = <GIC_SPI 68 IRQ_TYPE_EDGE_RISING>;
> + mboxes = <&apcs_glb 12>;
> + qcom,remote-pid = <1>;
> + label = "mpss";
> + };
> +
> + bam-dmux {
> + compatible = "qcom,bam-dmux";
> +
> + interrupt-parent = <&modem_smsm>;
> + interrupts = <1 IRQ_TYPE_EDGE_BOTH>, <11 IRQ_TYPE_EDGE_BOTH>;
> + interrupt-names = "pc", "pc-ack";
> +
> + qcom,smem-states = <&apps_smsm 1>, <&apps_smsm 11>;
> + qcom,smem-state-names = "pc", "pc-ack";
> +
> + dmas = <&bam_dmux_dma 4>, <&bam_dmux_dma 5>;
> + dma-names = "tx", "rx";
> };
> };
>
> ---
> base-commit: 3d6d817622b0a9721e3cc404df3469171582be13
> change-id: 20260727-shikra-pas-bam-dmux-binding-28a6bf97857c
>
> Best regards,
> --
> Vishnu Santhosh <vishnu.santhosh@oss.qualcomm.com>
>
prev parent reply other threads:[~2026-08-31 16:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 11:25 Vishnu Santhosh
2026-08-14 9:05 ` Krzysztof Kozlowski
2026-08-19 11:23 ` Vishnu Santhosh
2026-08-31 16:41 ` Bjorn Andersson
2026-08-31 16:44 ` Bjorn Andersson [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=apWuwq78D8lEBbeA@baldur \
--to=andersson@kernel.org \
--cc=bibek.patro@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=deepak.singh@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=komal.bajaj@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--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®