[Deepin-Kernel-SIG] [linux 6.6.y] [FROMLIST] dmaengine: qcom: gpi: set DMA_PRIVATE capability#1808
Conversation
The GPI DMA controller is only responsible for QUP peripherals, and cannot work as a general-purpose DMA accelerator. Set DMA_PRIVATE capability for it. This fixes error messages about GPI being shown when an async-tx consumer is loaded. Fixes: 5d0c353 ("dmaengine: qcom: Add GPI dma driver") Signed-off-by: Icenowy Zheng <zhengxingda@iscas.ac.cn> Link: https://lore.kernel.org/all/20260602070344.3707256-1-zhengxingda@iscas.ac.cn/ Suggested-by: Icenowy Zheng <zhengxingda@iscas.ac.cn> Signed-off-by: WangYuli <wangyl5933@chinaunicom.cn>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR updates the Qualcomm GPI DMA engine driver to mark it as a private DMA controller, restricting its use to QUP peripherals and preventing it from being treated as a general-purpose async-tx DMA provider. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Pull request overview
Marks the Qualcomm GPI DMAengine device as private so it won’t be considered by the generic async-tx DMA allocator/channel table, avoiding misleading “no DMA channels” style messages when unrelated async-tx consumers load. This aligns with GPI’s role as a QUP-peripheral-specific DMA controller rather than a general-purpose DMA engine.
Changes:
- Set the
DMA_PRIVATEcapability on the GPI DMA device during probe to keep it out of the general-purpose DMA allocation paths.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
The GPI DMA controller is only responsible for QUP peripherals, and cannot work as a general-purpose DMA accelerator.
Set DMA_PRIVATE capability for it.
This fixes error messages about GPI being shown when an async-tx consumer is loaded.
Fixes: 5d0c353 ("dmaengine: qcom: Add GPI dma driver")
Link: https://lore.kernel.org/all/20260602070344.3707256-1-zhengxingda@iscas.ac.cn/
Suggested-by: Icenowy Zheng zhengxingda@iscas.ac.cn
Summary by Sourcery
Bug Fixes: