From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Porting plat-pxa to the MMP PDMA driver
Date: Mon, 7 Apr 2014 15:02:56 +0100 [thread overview]
Message-ID: <20140407140256.GA13237@sirena.org.uk> (raw)
In-Reply-To: <5342A73F.8010907@zonque.org>
On Mon, Apr 07, 2014 at 03:25:19PM +0200, Daniel Mack wrote:
> On 04/07/2014 03:12 PM, Laurent Pinchart wrote:
> > 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).
> Yes, I've started working on this a long time ago, but got stuck because
> of the lack of support from users, as I don't have hardware with all
> possible DMA-capable components in use. Have a look here, the tree
> should be easily rebasable onto newer versions:
Is it not possible to do what we're doing with the Samsung platforms and
have both platform and generic DMA code in the source, selected via a
Kconfig symbol? That way you don't have to have a flag day.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140407/fa32b3aa/attachment.sig>
next prev parent reply other threads:[~2014-04-07 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 13:12 Porting plat-pxa to the MMP PDMA driver Laurent Pinchart
2014-04-07 13:25 ` Daniel Mack
2014-04-07 14:02 ` Mark Brown [this message]
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=20140407140256.GA13237@sirena.org.uk \
--to=broonie@kernel.org \
--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).