Hanno Braun

Sounds like there are two action items here: - Fix our API - Report the bug to NXP

Yes, good point. Updated title and labels accordingly.

Intra-doc links are stable now. Removing the `upstream` label.

I'm going to remove the `bug` label and replace it with `enhancement`. The USART code is not doing something wrong, it's just not enforcing one of its (documented) requirements. I...

I have more thoughts about baud rates: A device driver that communicates with its device via UART might need a specific baud rate to do so. It would be convenient,...

Hi @snakehand, thank your for opening this issue. Are you compiling with `--release`? I always assumed that the compiler would optimize this out, but looking at the code again, I'm...

~There's a problem with `LowPowerClock`: It starts with `clock::state::Disabled`, but that may be wrong, as we can't know what happened before the HAL was initialized.~ ~I'm not sure if that...

I've added support for additional low-power modes in #106.

Before trying to design anything that can be submitted to embedded-hal, at least #108, #109, and #110 should be resolved.

Two notes: - Before submitting this to embedded-hal, it would make sense to submit a power mode API first, as that's lower-level. See #3. - I'm not sure if this...