Hi Sandeep,
On Sat, Sep 12, 2009 at 21:50:44, Paulraj, Sandeep wrote:
> From: Sandeep Paulraj <[email protected]>
>
> This API is very similar to the edma_free_slot and
> edma_free_channel APIs. It is actually a consolidated
> version of these 2 APIs.
> A resource can be a channel or a slot.
> Using this API, the EDMA driver code makes the
> determination to free up a channel or a slot.
> The user does not have to decide the correct "free" API
> from among edma_free_channel or edma_free_slot.
>
> This API will be used by TI codecs and the DVSDK.
Hmm, wonder how it improves convenience considering
that channels and slots are allocated separately.
Presumably, user will need to maintain separate cookies
for channels and slots.
IMHO, in the absence of an alloc_resource() API, this
sounds incongruous.
[...]
> +/**
> + * edma_free_resource - deallocate DMA parameter RAM channel/resource
> + * @resource: Either a channel or a slot to be freed
> + *
> + * This deallocates the DMA channel and associated parameter RAM slot
> + * if the resource happens to be a channel, i.e if the resource number is
> + * less than 64 for DaVinci SOCs and less than 32 for Primus.
^^^^^^^
I think you mean to say DA8XX/OMAP-L1
Thanks,
Sekhar
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
