Here are the data structures with brief descriptions:

CIotAdcChain_t	Some ADC host controller supports grouping multiple ADC channels into a chain. When the chain is triggered to sample ADC data, all ADC channels in the group are sampled in sequence so that client doesn't need to trigger each channel individually. Coverted ADC samples from such chain group can be passed back to the client with a single callback. This data structure is used for ioctl to define ADC chain setting
CIotAdcChBuffer_t	Data structure for ioctl SetChBuffer setting channel data buffer is optional using this ioctl if client doesn't pass in data buffer for driver to use, callback is triggered for every ADC sample to pass data back to client as driver doesn't have buffer to accumulate data. As soon as callback returns, xConverted_Data becomes invalid. On the other hand however if client does pass a buffer for driver to use, callback is triggered only after driver has filled buffer with xBufLen samples, client buffer is passed back in callback as XConverted_Data whose life span is controlled by the client even after callback returns
CIotAdcChStatus_t	Data structure for ioctl GetChStatus
CIotAdcConfig_t	Data structures for ioctl request
CIotBatteryInfo_t	Battery information
CIotFlashInfo_t	Flash information
CIotFlashWriteProtectConfig_t	Flash protection configuration
CIotI2CConfig_t	I2C bus configuration
CIotI2sIoctlConfig_t	I2S configuration
CIotPowerWakeupSources_t	Wakeup source information
CIotPwmConfig_t	PWM configuration type
CIotRtcDatetime_t	RTC date and time format info
CIotSPIMasterConfig_t	The configuration parameters for SPI Master
CIotUARTConfig_t	Configuration parameters for the UART
CIotUsbDeviceEndpointConfig_t	Endpoint configuration structure
CIotUsbDeviceEndpointInfo_t	Endpoint status structure