> On Jun 2, 2016, at 5:07 PM, Sterling Hughes <[email protected]> wrote:
... > Right now, we don’t have a drivers interface, and the HAL is dual-purposing > both. The ADC is a good example of this, so I’ll focus in on that API. … > * The hal_adc_read() function blocks on read. This is for user convenience, > but does not represent how the underlying hardware implements an ADC read. Should we have non-blocking implementation available as well? IMHO, it’s easy to use non-blocking implementation in a blocking fashion, but doing it the other way around is not as easy. This is especially important with HALs which go over a bus (I2C, SPI). I admit, I don’t have much experience with use of ADC peripherals themselves. — M
