Skip to content
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

hw/mcu/dialog: Keep GPIO mux powered if non-GPIO pins enabled #2401

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andrzej-kaczmarek
Copy link
Contributor

If any pin has non-GPIO function we should not allow PD_COM to be
disabled since this will also reset GPIO mux settings and this can
lead to unpredictable behavior.

However, if there are no pins configured or all of them are used
as standard GPIO, we can just latch their state and disable PD_COM
safely.

If any pin has non-GPIO function we should not allow PD_COM to be
disabled since this will also reset GPIO mux settings and this can
lead to unpredictable behavior.

However, if there are no pins configured or all of them are used
as standard GPIO, we can just latch their state and disable PD_COM
safely.
@apache-mynewt-bot
Copy link

Style check summary

No suggestions at this time!

@@ -90,6 +90,7 @@ static struct hal_gpio_irq hal_gpio_irqs[HAL_GPIO_MAX_IRQ];
#if MYNEWT_VAL(MCU_GPIO_RETAINABLE_NUM) >= 0
static uint32_t g_mcu_gpio_latch_state[2];
static uint8_t g_mcu_gpio_retained_num;
static uint32_t g_mcu_gpio_can_sleep;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for now this variable is used only with values 0/1 maybe uint32_t is too much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants