From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: Add support for BCM2835.
Date: Wed, 13 Nov 2013 20:01:01 +0530 [thread overview]
Message-ID: <20131113143101.GD8834@intel.com> (raw)
In-Reply-To: <20131113145441.GQ878@sirena.org.uk>
On Wed, Nov 13, 2013 at 02:54:41PM +0000, Mark Brown wrote:
> On Wed, Nov 13, 2013 at 07:05:36PM +0530, Vinod Koul wrote:
> > On Wed, Nov 13, 2013 at 12:51:11PM +0000, Mark Brown wrote:
>
> > > I'm probably going to be looking at that at some point, though perhaps
> > > Martin will get to it since he seems to be looking at this.
>
> > Okay sounds good. This will also help in streamline the implementations..
>
> Yes, though I think some of the stuff Martin was talking about will need
> changes to the dmaengine APIs. He was wanting to reuse DMA lists which
> currently dmaengine needs to have built up each time.
Can you elobrate a bit more on what you guys want to do here?
--
~Vinod
-------------- 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/20131113/a7067c05/attachment.sig>
next prev parent reply other threads:[~2013-11-13 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 17:22 [PATCH] dmaengine: Add support for BCM2835 Florian Meier
2013-11-08 18:17 ` Mark Brown
2013-11-13 5:00 ` Vinod Koul
2013-11-13 12:51 ` Mark Brown
2013-11-13 13:35 ` Vinod Koul
2013-11-13 14:54 ` Mark Brown
2013-11-13 14:31 ` Vinod Koul [this message]
2013-11-13 16:30 ` Mark Brown
2013-11-08 19:11 ` Russell King - ARM Linux
2013-11-11 12:36 ` Florian Meier
2013-11-13 15:02 ` Tomasz Figa
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=20131113143101.GD8834@intel.com \
--to=vinod.koul@intel.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).