Albin Hedman

The main types the user will be passing around as of right now looks like this ```rust struct TimerDriver {...} struct Operator

> For now, let's just have `TimerDriver` suffixed with `*Driver`. Once this lands, we can revisit shortly after that. [...] Ok > * Why do we need `N`? `TimerConnection` is...

> Hey @usbalbin I'm looking to implement/leverage this as a pwm capture method, any pointers on where you left off? I have not really looked at the capture thing. However...

I am not working at this right now, and I do not see myself doing so anytime soon. So feel free to use this/finish it as you wish :)

Thank you for the feedback :) > TL;DR: Unsafe conversion from dynamic-sized iterator and safe conversion into a dynamic-sized iterator that the caller must make unsafe assertions about seems like...

I am happy to give implementing this a go if you think this would be a useful feature and anyone could give some sort of pointers as how/where this should...

I suppose this is also/could be related to #718

Related/duplicate of #133?

If this is something you want, do you have any pointers for where to begin(just in case I or someone else for that matter wants to give it a try)?...

Thank you! @Dirbaio > First step is to add the registers to [stm32-data](https://github.com/embassy-rs/stm32-data). See the ADC peripherals for C0 [have no `registers` field](https://github.com/embassy-rs/stm32-data-generated/blob/main/data/chips/STM32C031K6.json#L42) (compare it [with G0](https://github.com/embassy-rs/stm32-data-generated/blob/main/data/chips/STM32G031K8.json#L219) which does). [...]...