Ryan Summers

I'm in the process of bringing up a project using the STM32L452 and I'm starting to see the need here (e.g. SPI2 is not exposed via the HAL, but the...

This is a feature that I would like to see as well. It's very often the case with daughter boards where an I2C EEPROM or UID chip is polled to...

I don't think the intention here is to have the embedded HAL automatically detect the transaction failure, but rather have the `embedded-hal` provide a new API, such as: ```rust pub...

> > i2c_device.write([0xAB, 0xCD]).unwrap(); > > This will not work. If the MCU writes to the bus and detects that no device is present, this will happily panic your application,...

@hargoniX > I would not feel good about dropping this guarantee for all peripherals just because of FMC. When you refer to "this guarantee", I'm assuming you are referring to...

In the STM32H7xx-hal, we get around this by having the RCC constrain function return a PREC structure, which essentially provides a proxy into the RCC to enable and reset various...

@IamTheCarl Of relevance to this thread is the `embedded-nal` as well: https://github.com/rust-embedded-community/embedded-nal

I see no issue with adding these kind of examples to the main repository docs, and rust-doc would gladly accept examples. I'd be happy to review a PR for the...

The derive is done in `serde`, which doesn't care about the support of the underlying serialize/deserialize engine. Hence, we are just provided a serde-compatible API at the serde-json-core level. We...

0.5.0 sounds fine to me!