Input: bma150 - switch to using usleep_range instead of msleep
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>
This commit is contained in:
parent
1a9027770f
commit
f63bb4f442
|
@ -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;
|
||||
|
@ -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;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue