Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Platform support for Embedded targets #106
Platform support for Embedded targets #106
Changes from 110 commits
15690bb
bdd3c1f
6726fc9
6c7e6c6
b70632c
b683e61
f77809e
60304ce
cab3647
3faaad8
23673f0
2994d08
ad619dd
44663da
bd20b2d
d23bd40
b2ddd98
922fe32
ac0a936
d5074cd
2ce7bd0
c8d6a17
7a6559c
9729715
1760bce
a7d2029
12cc014
2749db8
3607d67
03ee757
9901a5c
3e1b8e7
7ee7106
f65a562
c0c8ab2
3798a3e
e8bf66a
cbd9c2c
b38adba
6360b3b
527959b
3c13193
a1e34da
fbcbb6f
9d5e2e4
e1d8cda
0a3df59
a7fd4aa
672562c
e92a153
2947e9e
8521421
8711abd
a4d822d
4e4f8f1
c48b3ad
8b1c518
d3a8f21
8b77ac7
468a5f4
4638f21
7b9b20f
a0a15ad
3e7e3f9
102fc00
488f6fd
d7797e8
3d96c9b
b05a5d7
31db8a4
2dba94b
7c143d8
23526a0
4fdf264
b01ef8e
a54a2e9
a7fb005
85ff383
d6e682d
09f336d
25dc3a6
192be4a
8bc911b
4614ec1
116d7ae
0f00fc3
254c3cf
f4dfb63
7c09642
87aa018
aa0efcb
5f11544
4d53c40
475235e
dc77d20
446f0c8
640e69f
46329ef
e96fddf
0fd8fba
b30684a
f1bcdc4
4754267
22406e3
c8b03e3
7057436
049aa99
4109b8d
8ca3d0f
b6d3a0e
56d0cbc
847b7ce
8361765
e0ea9a6
a91f605
ea29aad
70a8f77
af73a48
6369aa9
becb567
8962371
c58b354
073f175
965e9b2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
It looks like this function assumes that it is called from within a critical section.
If so, the comment should state that.
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.
Yes, sleep until is for internal use only and should only be called from a critical section, while advancing time. Maybe the API should be:
_lf_sleep_until_locked
?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.
A better design here would be to use an int for
_lf_in_critical_section
that counts nested calls. It should increment on each enter and decrement on each exit. Only when it hits zero should it re-enable interrupts. To address the FIXME in lf_critical_section_exit, in lf_critical_section_enter it could do something like this:Also, this and the next function should have comments. E.g.:
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.
Thanks for suggestion will add this!