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

LTIMER_OVERFLOW_EVENT vs LTIMER_TIMEOUT_EVENT documentation #52

Open
bennoleslie opened this issue Sep 27, 2020 · 0 comments
Open

LTIMER_OVERFLOW_EVENT vs LTIMER_TIMEOUT_EVENT documentation #52

bennoleslie opened this issue Sep 27, 2020 · 0 comments

Comments

@bennoleslie
Copy link

The exact semantics of this don't appear to be documented anywhere that I could find.

The semantics I assume is that if we ever have a timer overflow then some code will track the overflows to provide extended timer range, however while I can find implementations using it, I don't see anything that actually checks if they received and LTIMER_OVERFLOW_EVENT and doing anything about it.

I assume that LTIMER_TIMEOUT_EVENT should be used with the callback when a timeout set with ltimer_set_timeout occurs. I can't find where in the iMX timer implementations the LTIMER_TIMEOUT_EVENT is ever passed to the callback, but I may be looking in the wrong place.

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

No branches or pull requests

1 participant