From: vinod.koul@linux.intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V6 2/2] dmaengine: add helper function to request a slave DMA channel
Date: Tue, 16 Oct 2012 08:09:04 +0530 [thread overview]
Message-ID: <1350355144.1648.5259.camel@vkoul-udesk3> (raw)
In-Reply-To: <20121016024318.GF24393@S2101-09.ap.freescale.net>
On Tue, 2012-10-16 at 10:43 +0800, Shawn Guo wrote:
> On Tue, Sep 25, 2012 at 10:05:01AM +0530, Vinod Koul wrote:
> > On Mon, 2012-09-24 at 17:25 -0500, Jon Hunter wrote:
> > > > For DT bindings, I think the binding itself shouldn't change based on my
> > > > work but I would like these same bindings to help build the DMA engine
> > > > code mappings.
> > > >
> > > > Now would it make sense to NOT merge these changes for 3.7 and postpone
> > > > to 3.8. I can host these patches on a topic branch and merge them when
> > > > we are ready. I plan to spend some good amount of time on my work this
> > > > week so we should be ready pretty soon.
> > > > One these changes are merged, users can start moving to this scheme.
> > >
> > > I just wanted to see how things are progressing your side. Did you
> > > create a topic branch for this? If so let me know where I can find it, I
> > > did not find a branch on your infradead git tree.
> > >
> > > I wanted to pull in the latest patches for some testing.
> > Sorry for delay, I had everything ready, but couldn't manage to commit
> > and push. I have pushed to topic/dmaengine_dt, it is pushing out now...
> >
> Vinod,
>
> Looks it seemed 3.7-rc1. Does that mean we have to wait for 3.8, or
> will it show on later -rc for 3.7?
Yes this will be merged once we work out the common interface, otherwise
we will end up redoing interfaces for all drivers.
--
~Vinod
next prev parent reply other threads:[~2012-10-16 2:39 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 22:41 [PATCH V6 0/2] of: Add generic device tree DMA helpers Jon Hunter
2012-09-14 22:41 ` [PATCH V6 1/2] " Jon Hunter
2012-09-14 22:46 ` Stephen Warren
2012-09-15 0:14 ` Russell King - ARM Linux
2012-09-17 20:42 ` Arnd Bergmann
2012-09-17 23:06 ` David Brown
2012-09-18 12:50 ` Arnd Bergmann
2012-09-18 22:19 ` Mitch Bradley
2012-09-18 22:32 ` Russell King - ARM Linux
2012-09-19 11:09 ` Arnd Bergmann
2012-09-19 14:40 ` Mitch Bradley
2012-09-19 13:52 ` Matt Porter
2012-09-19 14:07 ` Matt Porter
2012-09-19 14:24 ` Arnd Bergmann
2012-09-19 14:36 ` Rob Herring
2012-09-19 14:40 ` Matt Porter
2012-09-19 14:50 ` Arnd Bergmann
2012-09-19 21:25 ` Mitch Bradley
2012-09-19 14:10 ` Rob Herring
2012-09-14 22:41 ` [PATCH V6 2/2] dmaengine: add helper function to request a slave DMA channel Jon Hunter
2012-09-17 3:33 ` Vinod Koul
2012-09-17 11:59 ` Arnd Bergmann
2012-09-17 22:36 ` Russell King - ARM Linux
2012-09-18 3:13 ` Vinod Koul
2012-09-18 13:21 ` Matt Porter
2012-09-18 15:20 ` Arnd Bergmann
2012-09-18 18:10 ` Russell King - ARM Linux
2012-09-24 22:25 ` Jon Hunter
2012-09-25 4:35 ` Vinod Koul
2012-10-16 2:43 ` Shawn Guo
2012-10-16 2:39 ` Vinod Koul [this message]
2012-11-09 20:01 ` Jon Hunter
2012-11-16 1:37 ` Vinod Koul
2012-11-16 8:39 ` Nicolas Ferre
2012-11-16 15:45 ` Jon Hunter
2012-11-28 17:06 ` Vinod Koul
2012-12-19 17:12 ` Jon Hunter
2012-12-20 14:57 ` Vinod Koul
2012-09-18 3:00 ` Vinod Koul
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=1350355144.1648.5259.camel@vkoul-udesk3 \
--to=vinod.koul@linux.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