Dániel Buga

I don't think this is as easy as you think, the peripherals can have multiple clock sources. Since we intend to support configuring clock sources, we'll have to somehow tie...

Which exact esp-hal version are you using?

I just quickly slapped the latest commit onto my toy device that has an I2C fuel gauge (a MAX17055 fwiw) and at least our async I2C isn't completely broken. I'll...

Unfortunately, the sample project you provided seems to work as expected for me - with the slight caveat that I'm using different hardware. I don't have your sensor, so just...

> I was referred to > > * https://github.com/card-io-ecg/card-io-fw/blob/main/embassy-alloc-taskpool/src/lib.rs > * https://github.com/card-io-ecg/card-io-fw/blob/main/macros/src/lib.rs > > Which together provide some kind of replacement for embassy `task` and allocation of memory for tasks....

> Does it make sense to be able to go back and forth between Blocking and Async, i.e will into_blocking also exist? Yes, although I'd imagine it would be rarely...

My PoV is that if the user binds a dma channel (like for SPI) then we use that over other async options. If not, then not - quite obviously.

> but I'd like leave enough time to do the impl before the 0.22 milestone is complete. Ambitious :D

> TX/RX only PARL_IO remain to be updated. I just realized that PARL_IO isn't a technical issue - tx/rx halves can be separately configured since their DMA channels are independent...

I don't see a simple way out of this without introducing our own, "PSRAM-safe" atomics. Which will be a usability and interoperability nightmare, because library developers will not likely use...