DCB Manager API Reference
Arguments
Table 5-1. Adi_dcb_Post Arguments
Argument
hServer
Priority
Callback
pHandle
u32Arg
pArg
Return Value
In debug mode, this routine returns one of the following result codes.
Otherwise,
ADI_DCB_RESULT_SUCCESS
ADI_DCB_RESULT_SUCCESS
ADI_DCB_RESULT_NO_MEMORY
ADI_DCB_RESULT_NO_SUCH_QUEUE
5-22
Explanation
Handle of the required queue server
Priority level at which the callback runs; the lower the number, the higher the
priority. There is no real limit on the value supplied.
Address of the client callback function queued
address passed as the first argument to the callback function upon its
void*
deferred execution. Typically it is a handle address that is meaningful within
the context of the callback function. For example, when used within the inter-
rupt handler of the DMA manager, this argument is the
defined when the DMA channel was opened.
value passed as the second argument to the callback function upon its
u32
deferred execution. (See
cally, it is a value that is meaningful within the context of the callback func-
tion. For example, when used within the interrupt handler of the DMA
manager, this argument describes the nature of the event that has occurred.
value passed as the third argument to the callback function upon its
void*
deferred execution. (See
cally, it is an address of a block of data. For example, when called within the
interrupt handler of the DMA manager, this argument points to the start of
the buffer for which the DMA transfer has completed.
Entry was successfully queued.
No vacant queue entry available.
Handle provided does not represent a valid queue
server.
VisualDSP++ 5.0 Device Drivers and System
"ADI_DCB_CALLBACK_FN" on page
"ADI_DCB_CALLBACK_FN" on page
is always returned.
Services Manual for Blackfin Processors
value
ClientHandle
5-25.) Typi-
5-25.) Typi-
Need help?
Do you have a question about the VisualDSP++ 5.0 and is the answer not in the manual?