Björn Quentin

> Oh, sorry. Haven't searched in PRs. No problem! 😄 > To make it work I should configure inversion on uart pins and then create a uart device? Yes, it...

> We don't even need these modules for anything, really. IIRC we introduced them to just have one `#[cfg(feature = "async")]` for the module - so yes, there is no...

That's a very nice project! 1. The only way right now would be to destroy the instance and re-create it 2. I guess yes - would be a nice enhancement...

So, I double checked some things Having 13-bit on ESP32-S3 is wrong since it _only_ supports 12-bit - but setting the bit-width is a no-op here - so it's not...

I also had a look and it's unfortunately under-documented in the TRM Another source to look at would be the NuttX implementation e.g. https://github.com/apache/nuttx/blob/master/arch/risc-v/src/esp32c3/esp32c3_adc.c for ESP32-C3. It might help a...

It's unfortunately undocumented as far as I can see I think there is some I2C bus and various things are controlled by it (obviously something about the ADC and also...

That's already awesome! Thanks for sharing your findings. I definitely understand you might not feel like continuing this journey but thankfully you shared your findings in a very accessible way...

I think @JurajSadel made some good progress in getting it to work for ESP32-C3 (which is IIRC what you urgently need). Maybe there is a branch you can already test

In future we _might_ add more ways to decide from which memory we need to allocate (not sure we need it but allowed alignment, able to execute code etc. comes...

Thanks for raising this issue. I'd say yes something like this would make sense for the case when the amount of data is less (or equal) than the FIFO size....