To publish this PR I had to learn git, GitHub, and a bunch of other things like ssh keys, tokens, etc etc
Honest, I have no idea what I need to fix in the failed checks, if someone would be so kind to help or simply tell me what I have to do I am more than happy to.

, I have no idea what I need to fix in the failed checks, if someone would be so kind to help or simply tell me what I have to do I am more than happy to.

Unfortunately the CI logs have been cleaned up, but if you rebase this commit and push again then it'll refresh.

The general docs for contributing are here: https://github.com/micropython/micropython/blob/master/CODECONVENTIONS.md

My guess is what you'll need to do is:

• Re-write the commit message to have a shorter first line, some short body description, and a Signed-off-by line. Look in the micropython git log for some examples of what it's looking for.
• Run uncrustify (see CODECONVENTIONS doc) and apply whatever small tweaks it makes to the C code formatting.

You should be able to use git commit --amend to apply the changes, then force-push the updated branch. Jim has a guide for this process at https://github.com/jimmo/git-and-micropython#README - or there are many non-MicroPython-specific guides out there.

Hi. Firstly thanks for all the work you guys did.on this but im still confused as to the current status. Simply put if i use the latest micropython build for an esp32 c3 and want to use deepsleep and wake on the state change of a gpio pin..(doesnt matter which one and it doesnt matter to my program which one woke it) , my application just needs to wake and connect to wifi and send some data... will it work?

@projectgus @m-cas
Some of the comments here make a lot of sense. What I think should be the correct solution:

• implement a esp32_wake_on_gpio like the esp32_wake_on_ext1, that sets the configuration in the struct
• implement support for the configuation in machine_sleep_helper
• add support for the wake reason
• optionally add support for the machine.pin_irq

All of these should use the capability definitions and not port definitions.

@projectgus please confirm that this makes sense to you, as I don't want to put effort into this and then have it go stale

@m-cas I don't think that your PR can be merged any more (wake_on_ext1 is now not available on ESP32C3 as EXT1 is not supported by the chip). I have here a PR (#17518) that add an interface for wake_on_gpio in a similar manner, I tested this on my C3, and it should work.
If you can compile from my branch, and test it as well, that would be very much appreciated.

I do see that in your PR you also have wake pins to see which pins triggered the waking up, I am happy to open a PR that will add those as well.

@meirarmon Good job! Please add the pin check on wake, it is as important as the wake function itself!-From my phone while mobile, please excuse any errors.On 20 Jun 2025, at 13:53, Meir Armon @.> wrote:meirarmon left a comment (micropython/micropython#15498) @m-cas I don't think that your PR can be merged any more (wake_on_ext1 is now not available on ESP32C3 as EXT1 is not supported by the chip). I have here a PR that add an interface for wake_on_gpio in a similar manner, I tested this on my C3, and it should work. If you can compile from my branch, and test it as well, that would be very much appreciated. I do see that in your PR you also have wake pins to see which pins triggered the waking up, I am happy to open a PR that will add those as well. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>

Hi, do you mean wake_gpio_pins and wake_ext1_pins?

@m-cas I have an open PR for the wake_pins function, you can see it here #17542. It is a separate PR than the wake_on_gpio (I don't want one feature to block the other if there are issues), but you have the following unified branch that you can compile and test with the two features together - https://github.com/meirarmon/micropython/tree/c3-wake-and-pins.