Meeting 2025-06-03

[adamgreig]

This is the agenda for the next meeting. Please add anything you'd like to discuss below!

• Meetings: Tuesday 8pm Europe/Berlin time
• Join the Matrix chat
• Nominated issues
• IRC/Matrix logs

[rmsyn]

I've made some progress on the SD/MMC traits + PoC implementations, and received some feedback from @bugadani + @MabezDev.

• recommendation to create an unstable crate in the embedded-hal workspace
  • sdio: initial SDIO HAL implementation esp-rs/esp-hal#3503 (comment)
  • sdio: initial SDIO HAL implementation esp-rs/esp-hal#3503 (comment)
  • sdio: initial SDIO HAL implementation esp-rs/esp-hal#3503 (comment)

Requesting feedback from the HAL team on their thoughts about creating the new unstable crate.

[romancardenas]

I think these two PRs are ready for review:

• Mark pre_init as deprecated cortex-m#598
• cortex-m-pac crate: standard traits and result handling for Cortex-M targets cortex-m#560

[jannic]

Ticket triage, this week looking at old tickets:

• Add example of opaque CountDown type usage embedded-hal#109
  can probably be closed - we no longer have a CountDown trait
• Add non-blocking spi::Send trait embedded-hal#121
  stalled in 2019 after some discussions didn't lead to an agreement. It's about embedded-hal-nb traits. Now that we have real async traits, I don't think anyone wants to spend time on controversial additions to embedded-hal-nb. Suggestion: Close.
• [WIP] Initial proposal for CancellableOneShot embedded-hal#124 → close, we don't have ADC traits any more
• TriStatePin proposal embedded-hal#157
  Not sure what to do about this one: Reading the comments, it looks like one main reason it was not merged is that Add digital::IoPin to resolve issue 29 embedded-hal#269 introduced IoPin which covers similar use cases. However, IoPin was removed again before e-h 1.0.
  As I understand it, the idea of having a tri-state pin (ie. [RFC] digital::TriStatePin embedded-hal#31) is still valid, but the implementation in TriStatePin proposal embedded-hal#157, adding a third variant Floating to PinState, would be a breaking change and is unlikely to be accepted. Maybe keep [RFC] digital::TriStatePin embedded-hal#31 open and close TriStatePin proposal embedded-hal#157?