dirbaio[m]: > <@dirbaio:matrix.org> also, there's more hard questions:
> 
> - does the trait model some "clock" that only counts up, or does it model a "timer" that the driver can restart at will?
> - what happens on overflow
> - can you make it count down and stop at 0 instead? this is how the embedded-hal 0.2 timer worked

- the relevant method to point 1, is `read_ticks`, and the output will be whatever the platform implementor deems. in the context of a clock, it would most likely be the contents of the corresponding register
- the effect of overflow would be up to the implementor. typically, it would be "whatever the hardware does"
- countdown would be outside of the scope, at least of initial work/design.