Thanks Dave, understood. See my reply to Kevin that I just sent, it explains that the LinuxUtils EDMA driver is probably unlike other drivers, in that it doesn't actually use any of the functional EDMA APIs, hence can treat slots and channels equivalently once they're allocated.
Regards, - Rob > -----Original Message----- > From: David Brownell [mailto:[email protected]] > Sent: Wednesday, September 16, 2009 1:49 PM > To: [email protected] > Cc: Tivy, Robert; Nori, Sekhar; Paulraj, Sandeep > Subject: Re: [PATCH] DaVinci: EDMA: New API edma_free_resource > > On Monday 14 September 2009, Tivy, Robert wrote: > > Without this API, in order to call either edma_free_slot() or > > edma_free_channel() the LinuxUtils EDMAK device driver will have to > > carry a "slot-vs-channel" "flag" or "cookie" around with the EDMA > > allocation record. > > It already needs one of those though doesn't it? You can't > use a slot to trigger a DMA transfer (keyed on an event, > manually, or by chaining). Unless it's been set up as a QDMA > channel... which and thus needs even more special handling > during deallocation. > > The reason there'is no edma_alloc_resource() is that there > really are two very distinct resource types, which need > distinct treatment almost everywhere. > > - Dave > > > _______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
