Device Manager Termination - Analog Devices VisualDSP++ 5.0 Service Manual

For example, if the client wants to initialize the device manager and would
have at most four device drivers open simultaneously at any point in time,
the amount of memory required is:
ADI_DEV_BASE_MEMORY+(ADI_DEV_DEVICE_MEMORY*4)).
When called, the initialization function,
memory that was passed in. Like all functions within the device manager,
the initialization function returns a return code that indicates success or
the specific error that occurred during the function call. All device man-
ager API functions return the
success. All error codes are in the form:
In addition to the return code, the
count of the number of device drivers it can manage simultaneously, and a
handle into the device manager. The device count can be tested to ensure
the device manager can control the requested number of device drivers.
Another parameter passed to the
region parameter. When it is necessary to protect a critical region of code,
the device manager and all physical drivers leverage the interrupt manager
system service to protect the critical code. The critical region parameter
passed into the
int_EnterCriticalRegion()
page 2-18.

Device Manager Termination

When the device manager is no longer needed, the client can terminate it
by means of the
the device manager handle, given to the client in the
function. The device manager closes any open physical devices and then
returns to the caller. After the return from the
VisualDSP++ 5.0 Device Drivers and System
Services Manual for Blackfin Processors
ADI_DEV_RESULT_SUCCESS
adi_dev_Init()
function is, in turn, passed to the
adi_dev_Init()
function. Refer to
adi_dev_Terminate()
Device Driver Manager
adi_dev_Init()
ADI_DEV_RESULT_XXXX
function returns a
adi_dev_Init()
function is a critical
"adi_int_Init" on
function. This function is passed
adi_dev_Init()
adi_dev_Terminate()
, initializes the
value to indicate
.
adi_
10-9