On 10/15/2012 09:39 PM, Vinod Koul wrote:

On Tue, 2012-10-16 at 10:43 +0800, Shawn Guo wrote:

quoted

On Tue, Sep 25, 2012 at 10:05:01AM +0530, Vinod Koul wrote:

quoted

On Mon, 2012-09-24 at 17:25 -0500, Jon Hunter wrote:

quoted

quoted

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.

Hi Vinod,

A few people have been asking me if getting device-tree support for DMA
engine is plan for record for v3.8. I know that you were working through
implementing a common interface and so I wanted to check how that is
going. Do you have any insight to when device-tree support may get added?

Cheers
Jon