1. 31 Jan, 2018 1 commit
  2. 30 Jan, 2018 2 commits
  3. 26 Jan, 2018 4 commits
  4. 24 Jan, 2018 1 commit
  5. 23 Jan, 2018 10 commits
  6. 19 Jan, 2018 2 commits
  7. 18 Jan, 2018 2 commits
  8. 17 Jan, 2018 9 commits
  9. 16 Jan, 2018 1 commit
  10. 12 Jan, 2018 1 commit
  11. 10 Jan, 2018 2 commits
    • Deepa Dinamani's avatar
      Input: extend usable life of event timestamps to 2106 on 32 bit systems · 152194fe
      Deepa Dinamani authored
      The input events use struct timeval to store event time, unfortunately
      this structure is not y2038 safe and is being replaced in kernel with
      y2038 safe structures.
      
      Because of ABI concerns we can not change the size or the layout of
      structure input_event, so we opt to re-interpreting the 'seconds' part
      of timestamp as an unsigned value, effectively doubling the range of
      values, to year 2106.
      
      Newer glibc that has support for 32 bit applications to use 64 bit
      time_t supplies __USE_TIME_BITS64 define [1], that we can use to present
      the userspace with updated input_event layout. The updated layout will
      cause the compile time breakage, alerting applications and distributions
      maintainers to the issue. Existing 32 binaries will continue working
      without any changes until 2038.
      
      Ultimately userspace applications should switch to using monotonic or
      boot time clocks, as realtime clock is not very well suited for input
      event timestamps as it can go backwards (see a80b83b7 "Input: evdev -
      add CLOCK_BOOTTIME support" by by John Stultz). With monotonic clock the
      practical range of reported times will always fit into the pair of 32
      bit values, as we do not expect any system to stay up for a hundred
      years without a single reboot.
      
      [1] https://sourceware.org/glibc/wiki/Y2038ProofnessDesignSuggested-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarDeepa Dinamani <deepa.kernel@gmail.com>
      Acked-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      Patchwork-Id: 10148083
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      152194fe
    • Hans de Goede's avatar
      Input: silead - add support for capactive home button found on some x86 tablets · eca3be9b
      Hans de Goede authored
      On some x86 tablets with a silead touchscreen the windows logo on the
      front is a capacitive home button. Touching this button results in a touch
      with bits 12-15 of the Y coordinates set, while normally only the lower 12
      are used.
      
      Detect this and report a KEY_LEFTMETA press when this happens. Note for
      now we only respond to the Y coordinate bits 12-15 containing 0x01, on some
      tablets *without* a capacative button I've noticed these bits containing
      0x04 when crossing the edges of the screen.
      Acked-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      eca3be9b
  12. 09 Jan, 2018 1 commit
  13. 05 Jan, 2018 2 commits
  14. 02 Jan, 2018 2 commits