[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1480354085-1885-1-git-send-email-a.mathur@samsung.com>
Date: Mon, 28 Nov 2016 22:58:05 +0530
From: Aniroop Mathur <a.mathur@...sung.com>
To: lost.distance@...oo.com, dmitry.torokhov@...il.com,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: s.samuel@...sung.com, r.mahale@...sung.com,
aniroop.mathur@...il.com, Aniroop Mathur <a.mathur@...sung.com>
Subject: [PATCH] Input: mouse: navpoint - Change msleep to usleep_range for small msecs
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, retry logic, etc.
Thus, change msleep to usleep_range for precise wakeups.
Signed-off-by: Aniroop Mathur <a.mathur@...sung.com>
---
drivers/input/mouse/navpoint.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/mouse/navpoint.c b/drivers/input/mouse/navpoint.c
index d6e8f58..2ede00b 100644
--- a/drivers/input/mouse/navpoint.c
+++ b/drivers/input/mouse/navpoint.c
@@ -166,7 +166,7 @@ static void navpoint_up(struct navpoint *navpoint)
for (timeout = 100; timeout != 0; --timeout) {
if (!(pxa_ssp_read_reg(ssp, SSSR) & SSSR_CSS))
break;
- msleep(1);
+ usleep_range(1000, 1100);
}
if (timeout == 0)
--
2.6.2
Powered by blists - more mailing lists