Driver Common Layer | Types

The following table lists types in this documentation.

A buffer type. 
Length of a buffer of VM_DCL_BUFFER type. 
The definition of the callback function used in DCL module. 
VM_DCL_CONTROL_COMMAND is the type used to represent the operations a driver needs to perform. The value of the variable of this type variable depends on specific device driver. Refer to the command enum of specific driver for detail. SIO: VM_DCL_SIO_CONTROL_COMMAND, I2C: VM_DCL_I2C_CONTROL_COMMAND, SPI: VM_DCL_SPI_CONTROL_COMMAND, ADC: VM_DCL_ADC_CONTROL_COMMAND, GPIO: VM_DCL_GPIO_CONTROL_COMMAND, PMU: VM_DCL_PMU_CONTROL_COMMAND, EINT: VM_DCL_EINT_CONTROL_COMMAND. 
VM_DCL_DEVICE is the type used to represent a specific device such as UART, I2C, GPIO and so on. Each device belongs to a specific device group. The value for a device group is defined in VM_DCL_DEVICE_GROUP. The value for a specific device is defined in the header file of that device. 
This is the event type to represent the change of a specific hardware condition, such as data transfer finished. An event is used to communicate asynchronously among the device operations. The value of each event is defined in VM_DCL_EVENT_VALUE
VM_DCL_FLAGS is the type used to represent the flags passed to the vm_dcl_open. The value of the flag depends on each specific device. 
VM_DCL_HANDLE is the type used to represent a specific device that is opened by vm_dcl_open. It is the return value of vm_dcl_open. The value will be passed to other API to tell the driver which device will respond to the corresponding operation. 
VM_DCL_OPTIONS is the type used to specify options to the read/write API. The value of the options depends on each specific device. 
Owner ID. 
Created with a commercial version of Doc-O-Matic. In order to make this message disappear you need to register this software. If you have problems registering this software please contact us at