Skip to content
  1. Dec 06, 2013
  2. Dec 02, 2013
    • Christian Engelmayer's avatar
      Input: usbtouchscreen - separate report and transmit buffer size handling · 4ef38351
      Christian Engelmayer authored
      
      
      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: default avatarChristian Engelmayer <christian.engelmayer@frequentis.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      4ef38351
    • Dmitry Torokhov's avatar
      Input: sur40 - suppress false uninitialized variable warning · b884eb8c
      Dmitry Torokhov authored
      
      
      We will never use packet_id before initializing it as we start with
      "need_blobs == -1" and will set packet_id there.
      
      Also use le32_to_cpu when fetching header->packet_id.
      
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      b884eb8c
  3. Nov 27, 2013
  4. Nov 26, 2013
  5. Nov 23, 2013
  6. Nov 21, 2013
  7. Nov 20, 2013
  8. Nov 15, 2013
  9. Nov 11, 2013
  10. Oct 31, 2013
  11. Oct 23, 2013
  12. Oct 16, 2013
  13. Oct 08, 2013
  14. Oct 07, 2013