From: Jan Kandziora <jjj@gmx.de>
To: linux-input@vger.kernel.org
Subject: Posiflex 0d3a:a000 touchscreen press not recognized in kernel 3.9.4
Date: Wed, 19 Jun 2013 09:12:05 +0200 [thread overview]
Message-ID: <51C159C5.7070702@gmx.de> (raw)
Hello,
I have a Posiflex 7215 POS system which has a USB touchscreen controller
onboard. I've done a kernel update from 2.6.35.4 to 3.9.4 and the touch
stopped working correctly. I tried with the generic usb hid driver, the
usbtouchscreen driver doesn't support this usb id. Evtest says:
# evtest /dev/input/event4
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0xd3a product 0xa000 version 0x110
Input device name: "Posiflex Inc. USB TOUCH V390"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 272 (LeftBtn)
Event code 273 (RightBtn)
Event code 274 (MiddleBtn)
Event type 3 (Absolute)
Event code 0 (X)
Value 2184
Min 0
Max 4095
Event code 1 (Y)
Value 3801
Min 0
Max 4095
Event type 4 (Misc)
Event code 4 (ScanCode)
Testing ... (interrupt to exit)
Event: time 1371798299.337455, type 3 (Absolute), code 0 (X), value 1596
Event: time 1371798299.337455, type 3 (Absolute), code 1 (Y), value 1969
Event: time 1371798299.337455, -------------- Report Sync ------------
There is no indication of pressure, so X is moving the cursor, but not
reporting anything pressed. With 2.6.35.4, there was a LeftBtn event
sent with each report block. Now it's gone.
What to do to make it work again?
Kind regards
Jan
next reply other threads:[~2013-06-19 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 7:12 Jan Kandziora [this message]
2013-06-19 7:50 ` Posiflex 0d3a:a000 touchscreen press not recognized in kernel 3.9.4 Benjamin Tissoires
[not found] ` <51C17882.4050206@gmx.de>
2013-06-19 15:56 ` Benjamin Tissoires
2013-06-19 16:42 ` Jan Kandziora
2013-06-19 21:54 ` Jiri Kosina
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=51C159C5.7070702@gmx.de \
--to=jjj@gmx.de \
--cc=linux-input@vger.kernel.org \
/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).