alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Florian Meier <florian.meier@koalo.de>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Dan Williams <dan.j.williams@intel.com>,
	linux-rpi-kernel <linux-rpi-kernel@lists.infradead.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
	Liam Girdwood <lgirdwood@gmail.com>,
	alsa-devel@alsa-project.org, Martin Sperl <martin@sperl.org>
Subject: Re: [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>

[-- Attachment #1: Type: text/plain, Size: 710 bytes --]

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

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  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
     [not found]   ` <20131108181743.GR2493-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13  5:00     ` Vinod Koul
     [not found]       ` <20131113050017.GO8834-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-11-13 12:51         ` Mark Brown
     [not found]           ` <20131113125111.GE878-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-11-13 13:35             ` Vinod Koul
2013-11-13 14:54               ` Mark Brown
2013-11-13 14:31                 ` Vinod Koul [this message]
     [not found]                   ` <20131113143101.GD8834-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-11-13 16:30                     ` Mark Brown
     [not found] ` <527D1DDA.2040004-oZ8rN/sblLk@public.gmane.org>
2013-11-08 19:11   ` Russell King - ARM Linux
     [not found]     ` <20131108191117.GT16735-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
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=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=florian.meier@koalo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=martin@sperl.org \
    --cc=swarren@wwwdotorg.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).