summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorChristian Engelmayer <christian.engelmayer@frequentis.com>2013-11-26 18:16:17 -0800
committerDmitry Torokhov <dmitry.torokhov@gmail.com>2013-12-01 22:18:04 -0800
commit4ef38351d770cc421f4a0c7a849fd13207fc5741 (patch)
treea367b5f06d4448aa9b5d172fd7cad6715a810390 /include
parentb884eb8c8502ca1fea497a02433c2b41de851f62 (diff)
Input: usbtouchscreen - separate report and transmit buffer size handling
This patch supports the separate handling of the USB transfer buffer length and the length of the buffer used for multi packet support. For devices supporting multiple report or diagnostic packets, the USB transfer size is now limited to the USB endpoints wMaxPacketSize - otherwise it defaults to the configured report packet size as before. This fixes an issue where event reporting can be delayed for an arbitrary time for multi packet devices. For instance the report size for eGalax devices is defined to the 16 byte maximum diagnostic packet size as opposed to the 5 byte report packet size. In case the driver requests 16 byte from the USB interrupt endpoint, the USB host controller driver needs to split up the request into 2 accesses according to the endpoints wMaxPacketSize of 8 byte. When the first transfer is answered by the eGalax device with not less than the full 8 byte requested, the host controller has got no way of knowing whether the touch controller has got additional data queued and will issue the second transfer. If per example a liftoff event finishes at such a wMaxPacketSize boundary, the data will not be available to the usbtouch driver until a further event is triggered and transfered to the host. From user perspective the BTN_TOUCH release event in this case is stuck until the next touch down event. Signed-off-by: Christian Engelmayer <christian.engelmayer@frequentis.com> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions