197 #ifndef ti_drivers_i2s_I2SCC26XX__include 198 #define ti_drivers_i2s_I2SCC26XX__include 252 uint8_t numberOfChannelsUsed;
255 } I2SCC26XX_DataInterface;
286 } I2SCC26XX_Interface;
323 uint8_t memorySlotLength;
342 uint8_t beforeWordPadding;
347 uint8_t afterWordPadding;
355 uint8_t dmaBuffSizeConfig;
367 uint16_t CCLKDivider;
376 uint16_t startUpDelay;
379 I2SCC26XX_DataInterface dataInterfaceSD0;
382 I2SCC26XX_DataInterface dataInterfaceSD1;
394 I2SCC26XX_Interface read;
397 I2SCC26XX_Interface write;
420 volatile bool i2sPowerConstraint;
HwiP structure.
Definition: HwiP.h:78
void(* I2S_Callback)(I2S_Handle handle, int_fast16_t status, I2S_Transaction *transactionPtr)
The definition of a user-callback function used by the I2S driver.
Definition: I2S.h:710
uint_least8_t pinWS
Definition: I2SCC26XX.h:239
void(* I2S_RegUpdate)(uint32_t ui32Base, uint32_t ui32NextPointer)
The definition of a function used to set the I2S register.
Definition: I2S.h:720
I2S Global configuration.
Definition: I2S.h:662
I2S_DataInterfaceUse
I2S data interface configuration.
Definition: I2S.h:822
I2S_PhaseType
I2S phase setting.
Definition: I2S.h:796
uint_least8_t pinSD1
Definition: I2SCC26XX.h:235
Semaphore module for the RTOS Porting Interface.
I2S_Role
I2S controller / target selection.
Definition: I2S.h:756
I2S Hardware attributes.
Definition: I2SCC26XX.h:233
uint_least8_t pinSCK
Definition: I2SCC26XX.h:237
uint8_t intPriority
Definition: I2SCC26XX.h:240
Inter-Integrated Circuit Sound (I2S) Bus Driver.
This file contains snippets to be used in the TI Driver s documentation *******************************************************************************TI Drivers is a collective of peripheral drivers for TI s SimpleLink portfolio The drivers are centered around a portable application programming TI Drivers are designed to be thread safe and work seamlessly inside of a real time operating and NoRTOS with examples provided for each variant the drivers are supported by SysConfig to enable easy re configuration of the drivers par and NoRTOS</b > li< b > Thread safe APIs</b > li< b > SysConfig support</b > li< b > Example usage</b > li< b > Power management support</b > par Driver Initialization parblock TI Driver APIs follow a common initialization model This model typically consists and close the driver Unless otherwise the initialization< b > may be called multiple times by the application It is only required that the initialization is done once For drivers which have an open< b > it must be called per instance of the driver to be used Each instance of the driver corresponds to a unique index in the ref< b > Driver_config</b > Multiple software entities may use the same driver concurrently For a Bluetooth or WiFi stack may utilize a driver instance The application may concurrently use the same driver assuming it has opened a unique instance of the driver Let s examine the ADC driver for example include Driver_init h A couple observations from this code we use the that s all we need for full details on the ADC and other reference the< b > Drivers and Documentation</b > section below endparblock *******************************************************************************The Display driver is designed abstract to operations &considerations specific to a given output method *******************************************************************************< TABLE >< TR align="center">< TH > Display Driver Interface</TH >< TH > Implementations</TH ></TR >< TR align="center">< TD > ref Display h</TD >< TD > ref DisplayHost h n ref DisplayUart2 h</TD ></TR ></TABLE > *******************************************************************************< TABLE >< TR align="center">< TH > Display Driver Interface</TH >< TH > Implementations</TH ></TR >< TR align="center">< TD > ref Display h</TD >< TD > ref DisplaySharp h n ref DisplayHost h n ref DisplayExt h n ref DisplayUart2 h</TD ></TR ></TABLE > *******************************************************************************Logging is a lightweight framework for instrumenting target code *******************************************************************************< TABLE >< TR align="center">< TH > Log Interface</TH >< TH > Sinks</TH ></TR >< TR align="center">< TD >< a class="el" href="../../../tiutils/html/group__ti__log__LOG.html"> Log h</a ></TD >< TD > ref LogSinkBuf h n ref LogSinkUART h</TD ></TR ></TABLE > *******************************************************************************< TABLE >< TR align="center">< TH > Log Interface</TH >< TH > Sinks</TH ></TR >< TR align="center">< TD >< a class="el" href="../../../tiutils/html/group__ti__log__LOG.html"> Log h</a ></TD >< TD > ref LogSinkBuf h n ref LogSinkUART h n ref LogSinkITM h</TD ></TR ></TABLE > *******************************************************************************The NoRTOS framework module is provided to enable use of drivers without an underlying operating system The module provides interfaces used by drivers to perform block register interrupts and more li ref NoRTOS h *******************************************************************************The Driver Porting NoRTOS</TD ></TR >< TR >< TD > ref EventP h</TD >< TD > Pendable bit event groups</TD >< TD > TI FreeRTOS</TD ></TR >< TR >< TD > ref HwiP h</TD >< TD > Hardware interrupt interface
Definition: doxygen_drivers.txt:196
I2S_ChannelConfig
Channels used selection.
Definition: I2S.h:856
Power notify object structure.
Definition: Power.h:441
I2S_SamplingEdge
I2S sampling setting.
Definition: I2S.h:769
void(* I2S_StopInterface)(I2S_Handle handle)
The definition of a function used to stop an I2S interface.
Definition: I2S.h:728
uint_least8_t pinSD0
Definition: I2SCC26XX.h:236
void(* I2SCC26XX_PtrUpdate)(I2S_Handle handle, I2SCC26XX_Interface *interface)
The definition of a function used by the I2S driver to refresh the pointer.
Definition: I2SCC26XX.h:298
uint_least8_t pinCCLK
Definition: I2SCC26XX.h:238
I2S transaction descriptor.
Definition: I2S.h:679
Hardware Interrupt module for the RTOS Porting Interface.