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

EXTI config for maxim, aducm3029 needs additional API call compared to stm32 #2423

Open
buha opened this issue Jan 28, 2025 · 0 comments
Open
Labels

Comments

@buha
Copy link
Contributor

buha commented Jan 28, 2025

As the title says, EXTI config for maxim and aducm3029 needs an additional no_os_gpio_direction_input() call compared to stm32 which does this in the HAL generated code, as specified in the .ioc.

Now there are 2 solutions which we should discuss here:

  1. Automatically perform this call for aducm3029 and maxim (and possibly others?) by adding this new feature.
  2. I'd argue that setting the GPIO as input is normal for any EXTI on any platform and probably there is no harm in recommending performing the step for stm32 too, but this has to be tested.
@buha buha added the question label Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant