Skip to content

Commit

Permalink
Input: bma150 - switch to using usleep_range instead of msleep
Browse files Browse the repository at this point in the history
msleep (1~20) may not do what the caller intends, and will often sleep
longer.  (~20 ms actual sleep for any value given in the 1~20ms range) This
is not the desired behaviour for many cases like device resume time, device
suspend time, device enable time, etc.  Thus, change msleep to usleep_range
for precise wakeups.

Signed-off-by: Aniroop Mathur <a.mathur@samsung.com>
Acked by: Albert Zhang <xu.zhang@bosch-sensortec.com>
Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
  • Loading branch information
Aniroop Mathur authored and Dmitry Torokhov committed Dec 27, 2016
1 parent 1a90277 commit f63bb4f
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions drivers/input/misc/bma150.c
Original file line number Diff line number Diff line change
Expand Up @@ -207,7 +207,7 @@ static int bma150_set_mode(struct bma150_data *bma150, u8 mode)
return error;

if (mode == BMA150_MODE_NORMAL)
msleep(2);
usleep_range(2000, 2100);

bma150->mode = mode;
return 0;
Expand All @@ -222,7 +222,7 @@ static int bma150_soft_reset(struct bma150_data *bma150)
if (error)
return error;

msleep(2);
usleep_range(2000, 2100);
return 0;
}

Expand Down

0 comments on commit f63bb4f

Please sign in to comment.