Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1531458 > unrolled thread
| Started by | Aniroop Mathur <a.mathur@samsung.com> |
|---|---|
| First post | 2016-11-28 18:20 +0100 |
| Last post | 2016-11-29 21:50 +0100 |
| Articles | 2 — 1 participant |
Back to article view | Back to linux.kernel
[PATCH] Input: mouse: navpoint - Change msleep to usleep_range for small msecs Aniroop Mathur <a.mathur@samsung.com> - 2016-11-28 18:20 +0100
Re: [PATCH] Input: mouse: navpoint - Change msleep to usleep_range for small msecs Aniroop Mathur <a.mathur@samsung.com> - 2016-11-29 21:50 +0100
| From | Aniroop Mathur <a.mathur@samsung.com> |
|---|---|
| Date | 2016-11-28 18:20 +0100 |
| Subject | [PATCH] Input: mouse: navpoint - Change msleep to usleep_range for small msecs |
| Message-ID | <sIxKW-4YT-21@gated-at.bofh.it> |
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@samsung.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
[toc] | [next] | [standalone]
| From | Aniroop Mathur <a.mathur@samsung.com> |
|---|---|
| Date | 2016-11-29 21:50 +0100 |
| Subject | Re: [PATCH] Input: mouse: navpoint - Change msleep to usleep_range for small msecs |
| Message-ID | <sIXvI-4Vd-21@gated-at.bofh.it> |
| In reply to | #1531458 |
Dear Mr. Paul Parsons,
I am Aniroop Mathur from Samsung R&D Institute, India.
I have submitted one patch as below for review to Linux Open Source.
The problem is that we do not have the hardware available with us to
test it and we would like to test it before actually applying it.
If you have the hardware available, could you please help to test this patch?
or could you provide contact points of individuals who could support to test it?
Thank you!
BR,
Aniroop Mathur
On Mon, Nov 28, 2016 at 10:58 PM, Aniroop Mathur <a.mathur@samsung.com> wrote:
> 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@samsung.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
>
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web