Albin Hedman

Correct me if I am wrong, but I do not think I am guilty to this one ```rust error[E0599]: no method named `split` found for struct `Serial` in the current...

@burrbull would you like to take a look at this?

There seems to be quite a lot of problems with [rm0366](https://www.st.com/resource/en/reference_manual/rm0366-stm32f301x68-and-stm32f318x8-advanced-armbased-32bit-mcus-stmicroelectronics.pdf) devices. Again I do not think I introduced those issues in this PR. (for example they not having spi1...

Thanks for the explanation!

> * What can you do with this API that you can't do with the `low_level` API? Safe construction with guardrails to prevent lots of configuration errors. > * Why...

> Perhaps it does not alleviate but what if the high level types where just very thin wrappers around custom timer? [...] On second thought, I suppose that is pretty...

Thanks for the read :) You absolutely have a point. I'll think about it

I have removed `CustomPwm` and turned the builder into one that builds a `low_level::Timer` instead. I have also removed all type arguments except `'d` and `T`. I have removed all...

Updated the above example(does not compile since not channels are done yet) ```rust let out_pin = PwmPin::new(out_pin, crate::gpio::OutputType::PushPull); let mut tim = CustomPwmBuilder::new(tim) //.frequency(Hertz(123)) .prescaler_and_period(0, 1337) .ch1_input_as_trigger( trigger_pin, FilterValue::FDTS_DIV32_N8, InputCaptureMode::BothEdges,...

Might have overdone the type level shenanigans a bit but #4895 is some sort of rough PoC thing to at least start a discussion.