lkml.org 
[lkml]   [2013]   [Feb]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH resent] dma: add the freescale-provided MultiChannel DMA driver
Hi Vinod,

On Thu, Feb 21, 2013 at 03:22:33PM +0530, Vinod Koul wrote:
> On Thu, Feb 21, 2013 at 09:29:47AM +0100, Philippe De Muyter wrote:
> > > 2. If you are not using dmaengine APIs then drivers/dma/ is not a place for you.
> >
> > What would be the place then for a multi-architecture dma driver. Freescale often
> > reuses the same blocks for its m68k (coldfire), powerpc and arm (iMX) product
> > lines. A dma driver with many similarities is already under the arch/powerpc
> > subtree. I would like to avoid that, because it clearly hurts reusability.
> So the question is will there be any more users of the driver other than the
> ethernet one? If No then it should live with ethernet driver.
>
> DMAengine framework should be used where you have a system dma controller used
> by different subsystems.

I am not aware of any other user now, and my unique motivation is to get
the ethernet driver into the kernel, for which this is a first step.

As it is clearly a dma driver, it seemed to me fit to place it under
drivers/dma, but I can understand that you disagree.

I only wanted, by placing this driver under drivers/dma, to make it more
visible, eventually getting some help to make it DMAengine enabled, and
to avoid the need to move the files when the DMAengine interface would
be added. So it is a chicken and egg question here :).

Again, thanks for your answers. Stany and I are trying since Aug 2012
to get those drivers (MCD dma and MCD_FEC ethernet) in the kernel.

Philippe

--
Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles


\
 
 \ /
  Last update: 2013-02-21 12:21    [W:0.062 / U:0.992 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site