// Configure the timer for each 500 milli to handle un-solicited events
TA1CCR0 = 0x4000;
// Handle any unsolicited event if required - the function shall be triggered few times in a second
hci_unsolicited_event_handler();
The above is from BasicWifiApplication,
and I now think it just calls the byte-parser for events twice a second and is actually NOT sending a read request to cc3000?
If the CC3000 have more event/un-solicited_events/data it will always keep IRQ low until its outgoing buffer is empty?
And I don't need to poll it a few times a second?
The mcu I use have hardware wait for IRQ-pin to be low (not just edge detection) it completely shuts down that part of the mcu to save power.
I can not wake up once it goes to sleep to periodically do spi hci reads, as that is not needed anyway?
