From: Alexander Gordeev <a.gordeev.box@gmail.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/2] dma: DMA slave device bringup tool
Date: Sat, 21 Feb 2026 14:22:46 +0100 [thread overview]
Message-ID: <20260221132248.17721-1-a.gordeev.box@gmail.com> (raw)
Hi All,
This is a custom tool that can be used to bring up DMA slave devices.
It consists of a user-level utility and a companion device driver that
communicate via IOCTL.
The tool is likely need some polishing, but I would like first get some
feedback to ensure there is interest.
I also tested it only on x86 and have little idea on how channel names
on other architectures look like. That could especially impact the way
dma_request_channel() treats user-provided target DMA channel names, as
exposed via /sys/class/dma.
Thanks!
Alexander Gordeev (2):
dmaengine/dma-slave: DMA slave device xfer passthrough driver
tools/dma-slave: DMA slave device transfer utility
drivers/dma/Kconfig | 7 +
drivers/dma/Makefile | 1 +
drivers/dma/dma-slave.c | 246 +++++++++++++++++++++++++
include/uapi/linux/dma-slave.h | 30 +++
tools/Makefile | 11 +-
tools/dma/Makefile | 20 ++
tools/dma/dma-slave.c | 321 +++++++++++++++++++++++++++++++++
7 files changed, 631 insertions(+), 5 deletions(-)
create mode 100644 drivers/dma/dma-slave.c
create mode 100644 include/uapi/linux/dma-slave.h
create mode 100644 tools/dma/Makefile
create mode 100644 tools/dma/dma-slave.c
--
2.51.0
next reply other threads:[~2026-02-21 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 13:22 Alexander Gordeev [this message]
2026-02-21 13:22 ` [RFC PATCH 1/2] dmaengine/dma-slave: DMA slave device xfer passthrough driver Alexander Gordeev
2026-02-21 13:22 ` [RFC PATCH 2/2] tools/dma-slave: DMA slave device transfer utility Alexander Gordeev
2026-02-24 22:34 ` [RFC PATCH 0/2] dma: DMA slave device bringup tool Frank Li
2026-02-25 9:37 ` Vinod Koul
2026-02-25 21:10 ` Alexander Gordeev
2026-02-26 7:07 ` Vinod Koul
2026-02-26 19:43 ` Alexander Gordeev
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=20260221132248.17721-1-a.gordeev.box@gmail.com \
--to=a.gordeev.box@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®