Re: [PATCH net-next v6 0/2] net: wwan: qcom_bam_dmux: Add restricted DMA pool support
From: patchwork-bot+netdevbpf
Date: Thu Nov 19 2026 - 05:20:16 EST
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@xxxxxxxxxx>:
On Thu, 12 Nov 2026 14:43:30 +0530 you wrote:
> Some Qualcomm SoCs, such as Shikra, run the modem in a separate security
> domain with restricted access to system memory. BAM-DMUX DMA mappings
> and BAM descriptor FIFOs must therefore be constrained to a designated
> memory region that can be shared with the modem. Accesses outside that
> region can trigger an XPU violation.
>
> Add memory-region and qcom,vmid properties to the BAM-DMUX binding, and
> a qcom,shikra-bam-dmux compatible that requires them. When qcom,vmid is
> present, the driver SCM-assigns the entire restricted DMA pool to the
> local and remote execution environments before requesting the DMA
> channels.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/2] dt-bindings: net: qcom,bam-dmux: Add memory-region and qcom,vmid properties
https://git.kernel.org/netdev/net-next/c/ed5087bd84ec
- [net-next,v6,2/2] net: wwan: qcom_bam_dmux: Assign restricted DMA pool to remote processor
https://git.kernel.org/netdev/net-next/c/a5ce83fc0b37
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html