AMiRo-OS

This is done via the optional AMIROOS_CFG_MAIN_LOOP_GPIOEVENT_FLAGSMASK macro,

which should be defined in the module.h file. Example:

  #define AMIROOS_CFG_MAIN_LOOP_GPIOEVENT_FLAGSMASK         \

    (AOS_GPIOEVENT_FLAG(padX) | AOS_GPIOEVENT_FLAG(padY) | AOS_GPIOEVENT_FLAG(padZ))

When AMIROOS_CFG_MAIN_LOOP_GPIOEVENT_FLAGSMASK has been defined correctly, the

main thread will be notified by the according events and execute its event

handling routine. Hence you have to implement another macro in module.h to

handle the custom event(s) appropriately: MODULE_MAIN_LOOP_GPIOEVENT(eventflags).

As you can see, the variable 'eventflags' is propagated to the hook. This

variable is a mask, that allows to identify the GPIO pad(s), which caused the

event, by the bits set. Following the example above, you can check which GPIOs

have caused events by using if-clauses in the implementation of the hook:

  #define MODULE_MAIN_LOOP_GPIOEVENT(eventflags) {          \

    if (eventflags & AOS_GPIOEVENT_FLAG(padX)) {            \

          AOS_GPIOEVENT_FLAG(padZ))) {                      \

2) define the AMIROOS_CFG_MAIN_LOOP_GPIOEVENT_FLAGSMASK macro.

3) implement the MODULE_MAIN_LOOP_GPIOEVENT(eventflags) hook.