linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: Porting plat-pxa to the MMP PDMA driver
Date: Mon, 07 Apr 2014 15:12:43 +0200	[thread overview]
Message-ID: <3296408.nMPs78xkYH@avalon> (raw)

Hello,

The MMP DMA (drivers/dma/mmap_pdma.c) driver supports the DMA engine found in 
PXA chips. However, PXA platforms still use a mix of custom platform code 
(arch/arm/plat-pxa/dma.c) and direct DMA controller access in various drivers 
(pata_pxa, spi-pxa2xx, pxa3xx_nand, pxaficp_ir, pxamci, smc91x, smc911x and 
pxa_camera).

I'd like to use the MMP PDMA driver through the DMA engine API in a new driver 
I'm writing instead of the legacy PXA DMA code. However, this requires porting 
the platform to the MMP PDMA driver first, which involves porting all the 
above drivers to the DMA engine API. The spi-pxa2xx driver has already been 
ported and currently supports both the legacy PXA DMA API and the DMA engine 
API. All the other drivers seem to require the legacy PXA DMA API.

I was wondering if any effort had been started in that direction. I could 
possibly help with the pxamci driver, but not with the other drivers as the 
corresponding peripherals are not used on my test platform (a custom PXA27x 
board).

-- 
Regards,

Laurent Pinchart

             reply	other threads:[~2014-04-07 13:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 13:12 Laurent Pinchart [this message]
2014-04-07 13:25 ` Porting plat-pxa to the MMP PDMA driver Daniel Mack
2014-04-07 14:02   ` Mark Brown
2014-04-07 14:11     ` Daniel Mack
2014-04-07 14:19       ` Mark Brown
2014-04-08  1:46   ` Laurent Pinchart

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=3296408.nMPs78xkYH@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).