wiseconnect: Resolved issues when multiple events are set in #143
Conversation
ragurram26
requested review from
jhedberg,
asmellby,
jerome-pouiller and
Martinhoff-maker
as code owners
ragurram26
force-pushed
the
event_flag_issue
branch
from
5f94abb to
68c73c7
Compare
|
Seems like this should have an Upstream-status trailer. I assume the corresponding fix has been submitted to wiseconnect upstream? |
ragurram26
force-pushed
the
event_flag_issue
branch
2 times, most recently
from
d8234fb to
8215c8a
Compare
…s events. It was observed that when one event is set and another event is subsequently set, the first event gets cleared prematurely before it can be processed. To address this, the osEventFlagsWait call was updated to use the osFlagsNoClear option, which prevents automatic clearing of events upon retrieval. Events are now manually cleared after they are read, ensuring that all set events are reliably processed and none are missed due to premature clearing caused by subsequent event updates. Signed-off-by: Rahul Gurram <[email protected]>
ragurram26
force-pushed
the
event_flag_issue
branch
from
8215c8a to
73d5ef2
Compare
It was observed that when one event is set and another event is subsequently set, the first event gets cleared prematurely before it can be processed. To address this, the osEventFlagsWait call was updated to use the osFlagsNoClear option, which prevents automatic clearing of events upon retrieval. Events are now manually cleared after they are read, ensuring that all set events are reliably processed and none are missed due to premature clearing caused by subsequent event updates. Same as been updated in the commit log |
si91x bus events.
Modified the osEventFlagsWait call to include the osFlagsNoClear option, which ensures that the events are not cleared automatically. After the events are received, manually clear them.