1. 01 Jul, 2015 1 commit
  2. 29 Jun, 2015 2 commits
  3. 25 Jun, 2015 3 commits
  4. 24 Jun, 2015 2 commits
  5. 22 Jun, 2015 3 commits
  6. 17 Jun, 2015 2 commits
  7. 16 Jun, 2015 2 commits
  8. 12 Jun, 2015 1 commit
    • Samuel Thibault's avatar
      Input: export LEDs as class devices in sysfs · f60c8ba7
      Samuel Thibault authored
      This change creates a new input handler called "leds" that exports LEDs on input
      devices as standard LED class devices in sysfs and allows controlling their
      state via sysfs or via any of the standard LED triggers. This allows to
      re-purpose and reassign LDEs on the keyboards to represent states other
      than the standard keyboard states (CapsLock, NumLock, etc).
      
      The old API of controlling input LEDs by writing into /dev/input/eventX
      devices is still present and will take precedence over accessing via LEDs
      subsystem (i.e. it may override state set by a trigger). If input device is
      "grabbed" then requests coming through LED subsystem will be ignored.
      Signed-off-by: default avatarSamuel Thibault <samuel.thibault@ens-lyon.org>
      Tested-by: default avatarPavel Machek <pavel@ucw.cz>
      Acked-by: default avatarPavel Machek <pavel@ucw.cz>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      f60c8ba7
  9. 11 Jun, 2015 2 commits
  10. 09 Jun, 2015 6 commits
  11. 02 Jun, 2015 2 commits
    • Dmitry Tunin's avatar
      Input: focaltech - report finger width to userspace · 85919a00
      Dmitry Tunin authored
      Focaltech touchpads report finger width in packet[5] of absolute packet.
      Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
      0xff is reported, when a large contact area is detected.
      This can be handled in userspace.
      Signed-off-by: default avatarDmitry Tunin <hanipouspilot@gmail.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      85919a00
    • Arnd Bergmann's avatar
      tty: remove platform_sysrq_reset_seq · ffb6e0c9
      Arnd Bergmann authored
      The platform_sysrq_reset_seq code was intended as a way for an embedded
      platform to provide its own sysrq sequence at compile time. After over two
      years, nobody has started using it in an upstream kernel, and the platforms
      that were interested in it have moved on to devicetree, which can be used
      to configure the sequence without requiring kernel changes. The method is
      also incompatible with the way that most architectures build support for
      multiple platforms into a single kernel.
      
      Now the code is producing warnings when built with gcc-5.1:
      
      drivers/tty/sysrq.c: In function 'sysrq_init':
      drivers/tty/sysrq.c:959:33: warning: array subscript is above array bounds [-Warray-bounds]
         key = platform_sysrq_reset_seq[i];
      
      We could fix this, but it seems unlikely that it will ever be used, so
      let's just remove the code instead. We still have the option to pass the
      sequence either in DT, using the kernel command line, or using the
      /sys/module/sysrq/parameters/reset_seq file.
      
      Fixes: 154b7a48 ("Input: sysrq - allow specifying alternate reset sequence")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      ffb6e0c9
  12. 26 May, 2015 4 commits
  13. 22 May, 2015 3 commits
  14. 21 May, 2015 3 commits
  15. 20 May, 2015 4 commits