Dario Nieuwenhuis

`ErrorKind::Interrupted` is annoying unix legacy-ish. I don't think anyone uses it intentionally anymore, especially now that async exists? it doesn't really exist on embedded, and i'd say it shouldn't exist....

probably, yes...

perhaps we can instead do the following: - Add a feature `portable-atomic` - Document that if you enable it, you have to add a dep on `portable-atomic` and enable one...

`embedded-storage` is not maintained by the WG. Perhaps this makes more sense to add in the `embedded-storage` repo instead?

pretty much all embassy crates have got a release over the past weeks, so now there's no advantage in using git. i'm going to close this issue, we should centralize...

Since this is a breaking change to `embassy-usb-driver` which is somewhat disruptive, i'd prefer to wait until at least one in-tree driver implements the `write()` API (and ideally demonstrates a...

marking as draft until [these](https://github.com/embassy-rs/embassy/pull/2799#issuecomment-2047530930) concerns are solved.

done in #3923

hey! did you write this manually? that file is autogenerated from https://github.com/embassy-rs/stm32-data/blob/main/data/registers/otg_v1.yaml . Could you add the missing registers there and then sync the generated code?

For qtaddr you can just make it a u32, and ensure in the driver the value you write is aligned. For `.as_value()` that match can be done in the driver...