From: Alexander Gordeev <a.gordeev.box@gmail.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: Frank Li <Frank.li@nxp.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] dma: DMA slave device bringup tool
Date: Thu, 26 Feb 2026 20:43:36 +0100 [thread overview]
Message-ID: <aaCiaMi5HV3dJNv7@ideapad> (raw)
In-Reply-To: <aZ_xQ8jk049d1OgW@vaman>
On Thu, Feb 26, 2026 at 12:37:47PM +0530, Vinod Koul wrote:
> > I likely missing something, but how this differs from dmatest, which also
> > lacks any controller-specific setup?
>
> slave dma needs a peripheral to test. For example a spi/i2c etc
> dmaengine in slave mode will not work untill unless there is some
> signalling for dmaengine from peripheral to push/pull data.
Well, the idea is to trigger xfers using custom out-of-band tooling.
> > I tested it on Avalon-MM Interface on Arria 10 FPGA and found it super-
> > useful - thus an attempt to share.
>
> Which driver is that? Seems more like a memcpy masked as slave to me
Yes, one could say so. It transfers off-CPU memory in one of FPGA
implementations, which does not need any xfer setup.
When attached to a camera however the xfer is triggered using a private
tool that uses i2c - exactly as you guys noticed.
The dmaengine driver for Avalon-MM Interface is not upstreamed yet.
> ~Vinod
Thanks!
prev parent reply other threads:[~2026-02-26 19:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-21 13:22 [RFC PATCH 0/2] dma: DMA slave device bringup tool Alexander Gordeev
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 [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=aaCiaMi5HV3dJNv7@ideapad \
--to=a.gordeev.box@gmail.com \
--cc=Frank.li@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.