mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-kernel@vger.kernel.org
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
	Dan Williams <dan.j.williams@intel.com>
Subject: dmaengine questions
Date: Thu, 12 Aug 2010 17:00:30 +0200	[thread overview]
Message-ID: <20100812150030.GB27749@pengutronix.de> (raw)

Hi,

I am currently looking into implementing the Freescale i.MX SDMA engine
into the dmaengine API. The SDMA engine can handle sg transfers from/to
devices. During implementation some questions came up.

On the i.MX we already have a DMA engine which can do slave dma
transfers, the IPU (drivers/dma/ipu/), which is exclusively used for
image operations. My problem is that I found no way for the clients
to select which DMA engine to use as both have the same capabilities
(DMA_SLAVE).

For the SDMA engine the clients have to pass some platform specific data
to the SDMA engine (dma request line, word width and the like). The
current mechanism is to pass this data through the dma_chan->private
field, which seems more like tunneling instead of passing the data as we
lose type safety. Are there any ideas to improve this?

Sascha



-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

             reply	other threads:[~2010-08-12 15:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 15:00 Sascha Hauer [this message]
2010-08-12 19:14 ` Dan Williams
2010-08-12 20:16   ` Sascha Hauer
2010-08-12 22:32     ` Linus Walleij
2010-08-13  7:40       ` Sascha Hauer

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=20100812150030.GB27749@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=dan.j.williams@intel.com \
    --cc=linus.ml.walleij@gmail.com \
    --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

all inboxes | Powered by JetHome®