GPIO device specific driver configuration structure. More...
#include <GPIOMSP432.h>
Data Fields | |
GPIO_PinConfig * | pinConfigs |
GPIO_CallbackFxn * | callbacks |
uint32_t | numberOfPinConfigs |
uint32_t | numberOfCallbacks |
uint32_t | intPriority |
GPIO device specific driver configuration structure.
The device specific GPIOMSP432_Config structure that tells the GPIO driver where the two aforementioned arrays are and the number of elements in each. The interrupt priority of all pins configured to generate interrupts is also specified here. Values for the interrupt priority are device-specific. You should be well-acquainted with the interrupt controller used in your device before setting this parameter to a non-default value. The sentinel value of (~0) (the default value) is used to indicate that the lowest possible priority should be used.
Below is an example of an initialized GPIOMSP432_Config structure:
GPIO_PinConfig* GPIOMSP432_Config::pinConfigs |
Pointer to the board's GPIO_PinConfig array
GPIO_CallbackFxn* GPIOMSP432_Config::callbacks |
Pointer to the board's GPIO_CallbackFxn array
uint32_t GPIOMSP432_Config::numberOfPinConfigs |
number of GPIO_PinConfigs defined
uint32_t GPIOMSP432_Config::numberOfCallbacks |
number of GPIO_Callbacks defined
uint32_t GPIOMSP432_Config::intPriority |
Interrupt priority used for call back interrupts
intPriority is the interrupt priority, as defined by the underlying OS. It is passed unmodified to the underlying OS's interrupt handler creation code, so you need to refer to the OS documentation for usage. If the driver uses the ti.dpl interface instead of making OS calls directly, then the HwiP port handles the interrupt priority in an OS specific way. In the case of the SYS/BIOS port, intPriority is passed unmodified to Hwi_create().
A setting of ~0 will configure the lowest possible priority.