-
Notifications
You must be signed in to change notification settings - Fork 8.4k
Add pit feature for mcxe31x #100752
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
base: main
Are you sure you want to change the base?
Add pit feature for mcxe31x #100752
Conversation
lucien-nxp
commented
Dec 9, 2025
- add some necessary static parameter for pit instances
- Enable counter_basic_api case by using pit0 instance
- Test counter_basic_api passed
- Update switch usage for mc_cgm_clock_control_on function - add pit clock on/get rate feature Signed-off-by: Lucien Zhao <[email protected]>
- add some necessary static parameter for pit instances - Enable counter_basic_api case by using pit0 instance - Test counter_basic_api passed Signed-off-by: Lucien Zhao <[email protected]>
|
| overdrive = <12>; | ||
| }; | ||
|
|
||
| &pit_0 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As pit is an optional counter, is it necessary to enable it on board level without any channel enabled?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think board level only enable instances, and set some specific parameter for this instance in specific application code(except if some common setting for this instances). Channel settings should be put into application level should be better because this should be determined by application code.


