lkml.org 
[lkml]   [2012]   [Mar]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH/RFC] dmaengine: add a slave parameter to __dma_request_channel()
From
Date
On Thu, 2012-03-08 at 14:18 +0100, Guennadi Liakhovetski wrote:
> > Assuming I didn't miss...
> >
> > The case B can be handled without sweat by platforms channel mapping
> > information.
> >
> > Case A where we don't find that devices exist in map, thus being treated
> > as generic DMA channels and can be handled easily in sequence. So when
> > someone in Q request a channel it would get first channel in Ps
> >
> > This way we handle both of them in a transparent manner to both clients
> > and controllers.
> >
> > Perhaps we can also add capability to know that if channel is to be
> > searched in map or not - would be anyway required for non slave cases.
>
> Right, but I don't understand then what this gives us. You propose some
> channel maps, that will not be used for your "case A." Which means, for
> "case A" nothing changes. So, the reason for this whole thread hasn't been
> addressed: how to pass channel configuration to the DMA controller driver.
For "Case A" there should be no filtering or any issues even now. You
have controller requesting a channel and as long as they get a channel
for respective pool, it should work.

Or is there anything else which is required in this case?


--
~Vinod



\
 
 \ /
  Last update: 2012-03-09 10:19    [W:0.120 / U:0.504 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site