Filter
Top Products
Getting Started with ADSP-BF548 EZ-KIT Lite 3-11
Using ADSP-BF548 EZ-KIT Lite Peripherals
as preparing the next data buffer. Such an operation can affect the
application’s response to interrupts from other peripherals. The
delayed callback manager provides a mechanism for drivers to place
a function pointer and associated arguments in a queue. The call-
back manager removes entries from the queue and calls the
functions at a later time when no other interrupts are being
serviced.
•
AD1980Callback: The ninth, and final, argument to
adi_dev_Open() is a pointer to the callback function
(AD1980Callback()) that we want the AD1980 driver to invoke.
See the callback function description on page 3-16 for more
information.
adi_dev_Control()—Configuring the Driver
The SSL’s device manager API has one function (adi_dev_Control()) for
configuring and controlling a device driver. An application can call
adi_dev_Control() multiple times in order to set up the operating param-
eters of the peripheral. Thereafter, the application uses the same function
to instruct the device manager to enable and disable data flow to and from
the peripheral, if required.
The adi_dev_Control() function takes three arguments:
• The first argument is the device handle returned by a successful call
to adi_dev_Open() (see Listing 3-1 on page 3-8). The value identi-
fies the device driver instance to the device manager.
• The second argument is an integer command value that specifies
the requested configuration or control action. There are two sets of
command values for adi_dev_Control().