-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Convert iwdg_stm32 STM32 Watchdog driver to new API #10917
Comments
@apodogrocki can you look at update the driver? |
I will do it |
@qianfan-Zhao I've already started working on that. If you would like you can think of adding window mode to the Independent Watchdog driver. It has never been activated, but can be useful. That probably requires separate PR. @erwango @galak There is also a question how to provide support for System Window Watchdog. All watchdog devices are named "WATCHDOG_0" at the moment. In case of STM32 can both IWDG & WWDG co-exist in the same time? Or Kconfig.stm32 should contain choice menu to select desired watchdog type? |
Currently the name of watchdog are defined in Kconfig. Based on the comments in #11331 we should remove the Kconfig options and make DT define the name of watchdog. Others SoC such as NRF has this lines in dts_fixup.h:
If there has 2 watchdogs, such as IWDG and WWDG, i think it OK to define the difference name in DT:
|
@qianfan-Zhao Ok, I see that you have better insight in the current Zephyr code than me. So maybe it is correct that you should take care of this task. After all it seems that @galak has already made a decision. |
Sorry, I got confused by the thread, and so I assigned it to @qianfan-Zhao. I'm happy for either of you guys to get this driver updated. I don't think @apodogrocki was a collaborator of the project, so couldn't add you :). |
Fixes: zephyrproject-rtos#10917 Signed-off-by: qianfan Zhao <[email protected]> Signed-off-by: Erwan Gouriou <[email protected]>
We have a new driver API for watchdog, the old API has been deprecated for several releases now. We need to convert the driver to use the API or remove it.
The text was updated successfully, but these errors were encountered: