What is the state of interupt-driven event handling?

[Ben-PH]

Specific to what I'm working on: A keyboard using keyberon. I'd like to have the keyboard in light-sleep, woken up when one of the input pins have a state change, scan the keyboard matrix and handle the results, then go back into light sleep.

I also have in mind a deep-sleep: given a few seconds of inactivity, drop into deep-sleep, getting woken up on a keyboard press. Going through crate documentation, and examples, I can't seem to find the things I need. (Though it could be I just don't know how/where to look. This world of embedded is a bit foreign to me). I found some examples using delay, and timer sleeps, but nothing that was just "sleep indefinately until interrupt from any of the gpio pins", for example.

I've seen that there are some recent PRs brought in relating to sleep, and that deep/light sleep impls are sortefd for esp-hal, but esp32cs-hal, specifically, is not checked off(#375).

Would be grateful for any information regarding the status, or anything that can point me in direction for me to get this rolling.

[MabezDev]

Not sure how to address this other than "it works" :D. We have raw interrupt support and also async support coming which will use interrupts behind the scenes to efficiently leverage the hardware. If you have more specific questions I'd be happy to help :).