Albin Hedman

This is probably what I stumbled (unknowingly) upon in in #78 . Great to hopefully have found the actual cause, my atempted fix perhaps only fixed the issue in my...

Judging by [example snippets in src/adc.rs](https://github.com/stm32-rs/stm32g4xx-hal/blob/main/src/adc.rs#L1074) that file might have been taken from another mcu and reworked for g4xx, could there been some incorrect assumptions made there?

What about going as far as something like [this](https://github.com/NandoBongers/stm32g4xx-hal/pull/1)?

I'm just a user, but from what I have seen so far this looks great. I really like not having 6 different modules with their own types. I also like...

I have now gotten rid of a few enums in favor of traits to force the user to pass a reference to the actual type instead of an enum variant....

@liamkinne or anyone, I am using this or rather [yet another branch](https://github.com/usbalbin/stm32g4xx-hal/tree/hrtim3) at work and I would at some point like to merge this or some future version of it....

Also I am using some of the not yet released features from the pac so depending a bit on when the next pac will be released I would prefer to...

Not sure how big the difference is between HRTIM in g4x4 vs f334 vs h7, but sure why not :)

> According to this (section 1.4): https://www.st.com/resource/en/application_note/an4539-hrtim-cookbook-stmicroelectronics.pdf > > There are only a few differences. Thats seems promising :) > tbh I would still go ahead an when it's ready...

Perhaps even a "offset" parameter. That, I, believe would be enough to allow scaling and moving around the curves above until they are all evenly spread out and with their...