Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
F
firmware
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Monitor
Service Desk
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
card10
firmware
Merge requests
!94
fix(ble): Do not try to schedule 0 tick WSF timers
Code
Review changes
Check out branch
Download
Patches
Plain diff
Merged
fix(ble): Do not try to schedule 0 tick WSF timers
schneider/ble-wsf-fix
into
master
Overview
1
Commits
1
Pipelines
3
Changes
1
Merged
schneider
requested to merge
schneider/ble-wsf-fix
into
master
5 years ago
Overview
1
Commits
1
Pipelines
3
Changes
1
Expand
0
0
Merge request reports
Compare
master
version 2
809dddb7
5 years ago
version 1
43c83a4b
5 years ago
master (base)
and
latest version
latest version
44d8adf6
1 commit,
5 years ago
version 2
809dddb7
1 commit,
5 years ago
version 1
43c83a4b
1 commit,
5 years ago
1 file
+
7
−
1
Inline
Compare changes
Side-by-side
Inline
Show whitespace changes
Show one file at a time
epicardium/ble/ble.c
+
7
−
1
Options
#include
"modules/log.h"
#include
"fs_util.h"
#include
"wsf_types.h"
#include
"wsf_buf.h"
#include
"wsf_trace.h"
@@ -162,6 +161,13 @@ static void scheduleTimer(void)
if
(
timerRunning
)
{
//printf("time_to_next_expire = %d\n", time_to_next_expire);
//printf("change period\n");
/* We need to make sure not to schedule a 0 ticks timer.
* Maybe it would also be enough to simply call the dispatcher
* in this case... */
if
(
time_to_next_expire
==
0
)
{
time_to_next_expire
=
1
;
}
if
(
timerWakeup
!=
NULL
)
{
xTimerChangePeriod
(
timerWakeup
,
Loading