kinetis/pit: Update Kconfig, implement oneshot PIT#18853
Conversation
linguini1
left a comment
There was a problem hiding this comment.
Well written and good test info! I would probably add your caveat about the bus speed to the RST docs for this chip.
|
Sorry @ghnotgood: CI Check failed because of |
You mean |
|
@ghnotgood please fix: |
I have added I have a question about the I think this should be fixed with How should I proceed? |
Good alternative! Thanks! |
|
Hi: Could you Rebase your PR with the Master Branch? We fixed the Config Error for esp32p4-function-ev-board. Thanks :-) |
273cb8f to
d88e970
Compare
|
@xiaoxiang781216 I have updated the length of the start of the comment blocks. However, please see #18863 Also, I have no idea why because the last char Thank you! |
|
@ghnotgood This will fix the long line. Thanks :-) static void
kinetis_oneshot_start(struct oneshot_lowerhalf_s *lower,
clkcnt_t delay_count)
{ |
Implementation of the Kinetis' Periodic Interrupt Timer (PIT). The lower half driver is oneshot. Signed-off-by: Jiri Vlasak <jvlasak@elektroline.cz>
|
@lupyuen I did it but I am very very sad. |
Implementation of the Kinetis' Periodic Interrupt Timer (PIT). The lower half driver is oneshot.
Summary
Kinetis' PIT is not yet implemented. It is simpler than FlexTimer Module (FTM) but good enough for oneshot timer-like use cases.
This PR implements Kinetis' PIT using oneshot count-based API.
Please, note that I am not completely sure about the
resolutionparameter of theoneshot_initializeprocedure. The frequency of the PIT depends on theBOARD_BUS_FREQand timing does not work as expected when something different is used. I am probably missing something and I am happy to fix it when I understand it. Thank you.Impact
Developers can
and then use
/dev/pit0as oneshot timer.Testing
With the changes to .config
I have run started our board:
and run the
oneshotexample:The delay between
Waiting...andFinishedwas approximately 2 seconds.