drivers/atwinc15x0: don't disable interrupts #18800
Merged
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.
Contribution description
Globally disabling interrupts is very bad if done for an extended period of times.
Here
atwinc15x0
would disable interrupts for up to 55µs which leads to lost bytes when used with UART based interfaces like SLIP or DOSE.When looking at the code it's not clear why the interrupts were disabled in the first place. Only the
atwinc15x0
thread itself will interact with the data, even if there is a GPIO interrupt from the module it will only callnetdev_trigger_event_isr()
which adds an entry to the event queue to be processed by theatwinc15x0
thread.Testing procedure
I ran
examples/gnrc_networking
withand
in parallel with no ill effects.
Issues/PRs references