-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ability to read GPIO holder status (IDFGH-14018) #14841
Comments
There is a related function, |
From your PR description, I get your scenario is you need to hold the SPI LCD CS line during a restart (core reset), is that correct? Though you have held the CS pad before restart, after the system restarts, all the signal connection information will still get lost, so you will still have to re-configure the pin (assuming you are using Is there any reason why you don't want to call |
Hi @songruo , It's close but not exactly what you described. I'm using If the CS/RST pins were held with pin-holders, then I know an earlier software run has already configured the display, so I need to avoid calling If the CS/RST were not held with pin-holders, then the display needs to be fully booted, with |
@bryghtlabs-richard Do you think checking the chip reset reason with esp_rom_get_reset_reason() can also achieve the purpose? |
Is your feature request related to a problem?
I need the ability to read the GPIO holder status per pin, so that I can discover the state of different peripherals after a restart.
Describe the solution you'd like.
I'd like a nice ESP-IDF GPIO interface to take a GPIO number and receive a boolean value if the pin-holder was enabled or disabled.
Describe alternatives you've considered.
No response
Additional context.
No response
The text was updated successfully, but these errors were encountered: