From: Florian Echtler <floe@butterbrot.org>
To: linux-media@vger.kernel.org, hverkuil@xs4all.nl
Cc: linux-input@vger.kernel.org,
Florian Echtler <floe@butterbrot.org>,
Martin Kaltenbrunner <modin@yuri.at>
Subject: [PATCH v2 2/3] sur40: lower poll interval to fix occasional FPS drops to ~56 FPS
Date: Tue, 31 May 2016 22:15:32 +0200 [thread overview]
Message-ID: <1464725733-22119-2-git-send-email-floe@butterbrot.org> (raw)
In-Reply-To: <1464725733-22119-1-git-send-email-floe@butterbrot.org>
The framerate sometimes drops below 60 Hz if the poll interval is too high.
Lowering it to the minimum of 1 ms fixes this.
Signed-off-by: Martin Kaltenbrunner <modin@yuri.at>
Signed-off-by: Florian Echtler <floe@butterbrot.org>
---
drivers/input/touchscreen/sur40.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/touchscreen/sur40.c b/drivers/input/touchscreen/sur40.c
index 4b1f703..64e588c 100644
--- a/drivers/input/touchscreen/sur40.c
+++ b/drivers/input/touchscreen/sur40.c
@@ -126,7 +126,7 @@ struct sur40_image_header {
#define VIDEO_PACKET_SIZE 16384
/* polling interval (ms) */
-#define POLL_INTERVAL 4
+#define POLL_INTERVAL 1
/* maximum number of contacts FIXME: this is a guess? */
#define MAX_CONTACTS 64
--
1.9.1
next prev parent reply other threads:[~2016-05-31 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 20:15 [PATCH v2 1/3] sur40: properly report a single frame rate of 60 FPS Florian Echtler
2016-05-31 20:15 ` Florian Echtler [this message]
2016-05-31 20:15 ` [PATCH v2 3/3] sur40: fix occasional oopses on device close Florian Echtler
2016-07-05 6:41 ` [PATCH v2 1/3] sur40: properly report a single frame rate of 60 FPS Hans Verkuil
2016-07-05 6:56 ` Florian Echtler
2016-07-05 7:06 ` Hans Verkuil
2016-07-06 8:40 ` Hans Verkuil
2016-07-06 20:51 ` Florian Echtler
2016-07-07 6:35 ` Hans Verkuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1464725733-22119-2-git-send-email-floe@butterbrot.org \
--to=floe@butterbrot.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=modin@yuri.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).