summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAniroop Mathur <a.mathur@samsung.com>2016-12-27 13:22:42 -0800
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2016-12-27 13:36:50 -0800
commitf63bb4f442d6c7929e58d671d1f46e122c441884 (patch)
treeedf49e69fb0e9f97772b6e9de3b63fcc188bb0dc
parent1a9027770f3d93b78f7031af79597f9659db5d70 (diff)
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>
-rw-r--r--drivers/input/misc/bma150.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/input/misc/bma150.c b/drivers/input/misc/bma150.c
index 2124390ec38c..1fa85379f86c 100644
--- a/drivers/input/misc/bma150.c
+++ b/drivers/input/misc/bma150.c
@@ -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;
}