From: Vinod Koul <vkoul@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [PATCH 3/3] dmaengine: qcom: bam_dma: convert tasklet to a workqueue
Date: Sat, 22 Nov 2025 14:40:04 +0530 [thread overview]
Message-ID: <aSF97DVdACd7h-LI@vaman> (raw)
In-Reply-To: <20251106-qcom-bam-dma-refactor-v1-3-0e2baaf3d81a@linaro.org>
On 06-11-25, 16:44, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
>
> There is nothing in the interrupt handling that requires us to run in
> atomic context so convert the tasklet to a workqueue.
The reason dmaengine drivers use tasklets is higher priority to handle
dma interrupts... This is by design for this subsystem.
There was an attempt in past to do conversion away from tasklets [1]:
We need something similar apprach here. I can queue up first two though
1: https://lore.kernel.org/all/20240327160314.9982-1-apais@linux.microsoft.com/
--
~Vinod
next prev parent reply other threads:[~2025-11-22 9:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 15:44 [PATCH 0/3] dmengine: qcom: bam_dma: some driver refactoring Bartosz Golaszewski
2025-11-06 15:44 ` [PATCH 1/3] dmaengine: qcom: bam_dma: order includes alphabetically Bartosz Golaszewski
2025-11-12 3:11 ` Dmitry Baryshkov
2025-11-06 15:44 ` [PATCH 2/3] dmaengine: qcom: bam_dma: use lock guards Bartosz Golaszewski
2025-11-06 15:44 ` [PATCH 3/3] dmaengine: qcom: bam_dma: convert tasklet to a workqueue Bartosz Golaszewski
2025-11-12 3:10 ` Dmitry Baryshkov
2025-11-12 16:19 ` Bjorn Andersson
2025-11-13 10:26 ` Bartosz Golaszewski
2025-11-22 9:10 ` Vinod Koul [this message]
2025-11-24 7:58 ` Bartosz Golaszewski
2025-12-16 16:59 ` (subset) [PATCH 0/3] dmengine: qcom: bam_dma: some driver refactoring Vinod Koul
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=aSF97DVdACd7h-LI@vaman \
--to=vkoul@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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