TI Deep Learning Product User Guide
TIDL_DataflowInitParams Struct Reference

Detailed Description

A structure for a 3 dimensional buffer descriptor.

This structure define the parameters needed during TIDL_DataflowInit function call.

Data Fields

int32_t dataFlowType
 
TIDL_DataflowKernelGetHandleSize getHandleSize
 
TIDL_DataflowKernelInitFuncPtr initFuncPtr
 
TIDL_DataflowKernelExecFuncPtr execFuncPtr
 
void * kernelInitArgs
 

Field Documentation

◆ dataFlowType

int32_t TIDL_DataflowInitParams::dataFlowType

Number of input tensors for the processing eTIDL_DataFlowType

◆ getHandleSize

TIDL_DataflowKernelGetHandleSize TIDL_DataflowInitParams::getHandleSize

Function pointer to get the kernel's handle size requirement. This can be given as Null if kernel doesn't need any handle

◆ initFuncPtr

TIDL_DataflowKernelInitFuncPtr TIDL_DataflowInitParams::initFuncPtr

Function pointer for the kernel's Intilization call. User is expected to implement their kernel by adhering to the srcAddr and dstAddr dimensions as TIDL will internally call this function to handle changes in dimensions based on various regions of processing. This can be given as NULL if kernel doesn't need any handle. When this is NULL then user is expected to implement its kernel by handling all the dimensions as give srcAddr and dstAddr parameter in execute call. Given that execute call is called mutliple times, user can avoid computation in execute call by providing a valid initFuncPtr

◆ execFuncPtr

TIDL_DataflowKernelExecFuncPtr TIDL_DataflowInitParams::execFuncPtr

Function pointer for the kernel's execute call. This cannot be given as NULL. If initFuncPtr is NULL then user is expected to adhere to the srcAddr and dstAddr arguments. If initFuncPtr is not NULL then user can ignore these two parameters during execute call

◆ kernelInitArgs

void* TIDL_DataflowInitParams::kernelInitArgs

Pointer to pass any arguments to the ther kernel. This pointer will be passed as it is to the initFuncPtr. If this information is required for the execute call then user is expected to store this in its internal handle.