From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: Add hisilicon k3 DMA engine driver
Date: Fri, 21 Jun 2013 16:19:16 +0530 [thread overview]
Message-ID: <20130621104916.GI23141@intel.com> (raw)
In-Reply-To: <3686094.n3OCaPGG8M@wuerfel>
On Tue, Jun 18, 2013 at 05:08:01PM +0200, Arnd Bergmann wrote:
> On Tuesday 18 June 2013 22:22:17 zhangfei wrote:
> > > With no need to have a filter function.
> >
> > Cool, then I would like to wait for the patch.
>
> Maybe you can try to add the dma_get_slave_channel() function I proposed here
> as a first patch and add your driver on top. There may be issues I missed,
> and Vinod needs to agree to the concept first, but that would probably
> get his attention.
You have it now :)
>
> Or you could send your the new interface as an add-on patch
> and convert your driver along with adding it.
patch is always welcome
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: zhangfei <zhangfei.gao-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
device-tree
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
Russell King - ARM Linux
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
zhangfei gao
<zhangfei.gao-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] dmaengine: Add hisilicon k3 DMA engine driver
Date: Fri, 21 Jun 2013 16:19:16 +0530 [thread overview]
Message-ID: <20130621104916.GI23141@intel.com> (raw)
In-Reply-To: <3686094.n3OCaPGG8M@wuerfel>
On Tue, Jun 18, 2013 at 05:08:01PM +0200, Arnd Bergmann wrote:
> On Tuesday 18 June 2013 22:22:17 zhangfei wrote:
> > > With no need to have a filter function.
> >
> > Cool, then I would like to wait for the patch.
>
> Maybe you can try to add the dma_get_slave_channel() function I proposed here
> as a first patch and add your driver on top. There may be issues I missed,
> and Vinod needs to agree to the concept first, but that would probably
> get his attention.
You have it now :)
>
> Or you could send your the new interface as an add-on patch
> and convert your driver along with adding it.
patch is always welcome
--
~Vinod
next prev parent reply other threads:[~2013-06-21 10:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 4:54 [PATCH] dmaengine: Add hisilicon k3 DMA engine driver Zhangfei Gao
2013-06-17 4:54 ` Zhangfei Gao
2013-06-17 20:58 ` Arnd Bergmann
2013-06-17 20:58 ` Arnd Bergmann
2013-06-18 2:33 ` zhangfei gao
2013-06-18 2:33 ` zhangfei gao
2013-06-18 14:09 ` Arnd Bergmann
2013-06-18 14:09 ` Arnd Bergmann
2013-06-18 14:22 ` zhangfei
2013-06-18 14:22 ` zhangfei
2013-06-18 15:08 ` Arnd Bergmann
2013-06-18 15:08 ` Arnd Bergmann
2013-06-21 10:49 ` Vinod Koul [this message]
2013-06-21 10:49 ` Vinod Koul
2013-06-21 10:45 ` Vinod Koul
2013-06-21 10:45 ` Vinod Koul
2013-06-21 10:43 ` Vinod Koul
2013-06-21 10:43 ` Vinod Koul
2013-06-21 11:41 ` Arnd Bergmann
2013-06-21 11:41 ` Arnd Bergmann
2013-06-24 8:49 ` zhangfei gao
2013-06-24 8:49 ` zhangfei gao
2013-06-24 16:15 ` Arnd Bergmann
2013-06-24 16:15 ` Arnd Bergmann
2013-06-25 5:34 ` zhangfei gao
2013-06-25 5:34 ` zhangfei gao
2013-06-21 10:40 ` Vinod Koul
2013-06-21 10:40 ` Vinod Koul
2013-06-25 5:34 ` zhangfei gao
2013-06-25 5:34 ` zhangfei gao
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=20130621104916.GI23141@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.