All of lore.kernel.org
 help / color / mirror / Atom feed
From: "François Legal" <devel@thom.fr.eu.org>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: Doing DMA from peripheral to userland memory
Date: Fri, 27 Aug 2021 15:44:42 +0200	[thread overview]
Message-ID: <1202-6128ec80-1e5-1ab27320@266372968> (raw)
In-Reply-To: <87v93rjb2o.fsf@xenomai.org>

Le Vendredi, Août 27, 2021 15:01 CEST, Philippe Gerum <rpm@xenomai.org> a écrit:

>
> François Legal via Xenomai <xenomai@xenomai.org> writes:
>
> > Hello,
> >
> > working on a zynq7000 target (arm cortex a9), we have a peripheral that generates loads of data (many kbytes per ms).
> >
> > We would like to move that data, directly from the peripheral memory (the OCM of the SoC) directly to our RT application user memory using DMA.
> >
> > For one part of the data, we would like the DMA to de interlace that data while moving it. We figured out, the PL330 peripheral on the SoC should be able to do it, however, we would like, as much as possible, to retain the use of one or two channels of the PL330 to plain linux non RT use (via dmaengine).
> >
> > My first attempt would be to enhance the dmaengine API to add RT API, then implement the RT API calls in the PL330 driver.
> >
> > What do you think of this approach, and is it achievable at all (DMA directly to user land memory and/or having DMA channels exploited by xenomai and other by linux) ?
> >
> > Thanks in advance
> >
> > François
>
> As a starting point, you may want to have a look at this document:
> https://evlproject.org/core/oob-drivers/dma/
>
> This is part of the EVL core documentation, but this is actually a
> Dovetail feature.
>

Well, that's quite what I want to do, so this is very good news that it is already available in the future. However, I need it through the ipipe right now, but I guess the process stays the same (through patching the dmaengine API and the DMA engine driver).

I would guess the modifications to the DMA engine driver would be then easily ported to dovetail ?

François

> --
> Philippe.



  reply	other threads:[~2021-08-27 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27  9:29 Doing DMA from peripheral to userland memory François Legal
2021-08-27 13:01 ` Jan Kiszka
2021-08-27 13:01 ` Philippe Gerum
2021-08-27 13:44   ` François Legal [this message]
2021-08-27 13:54     ` Philippe Gerum
2021-08-27 14:09       ` François Legal
2021-08-27 14:36         ` Philippe Gerum
2021-08-31  9:36           ` François Legal
2021-08-31 17:37             ` Philippe Gerum
2021-09-01  8:24               ` François Legal
2021-09-02 16:41                 ` François Legal
2021-09-02 17:12                   ` Philippe Gerum

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=1202-6128ec80-1e5-1ab27320@266372968 \
    --to=devel@thom.fr.eu.org \
    --cc=rpm@xenomai.org \
    --cc=xenomai@xenomai.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.