Fix for async events being processed twice.

chprintfs in the handler are presumably permitting another thread to run
when they DMA data over SPI.
If another thread is waiting on an event then permitting it to run here
will cause it to also enter the async cb.
This is a hacky fix for the time being - redefining the print macro.