1. 27 11月, 2013 1 次提交
  2. 27 8月, 2013 1 次提交
  3. 03 6月, 2013 1 次提交
  4. 12 3月, 2013 1 次提交
    • D
      Input: add IMS Passenger Control Unit driver · 628329d5
      Dmitry Torokhov 提交于
      The PCU is a device installed in the armrest of a plane seat and
      is connected to IMS Rave Entertainment System. It has a set of control
      buttons (Volume Up/Down, Attendant, Lights, etc) on one side and
      gamepad-like controls on the other side.
      
      Originally the device was handled from userspace and because of that
      it presents itself on USB bus as a CDC-ACM modem device that however
      can not make calls. However the custom handling is not as convenient
      as using standard input subsystem facilities. If it was pure input
      device it would be possible to continue using userspace solution
      (moving it over to uinput), but the device also has backlighted keys
      which can not be supported via uinput.
      Signed-off-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      628329d5
  5. 28 11月, 2012 1 次提交
    • M
      Input - arizona-haptics: Add driver haptics module on Arizona CODECs · 9dd555e2
      Mark Brown 提交于
      The Arizona CODECs contain a haptics module providing vibration feedback
      support. Implement basic support for this, providing simple start/stop and
      signal magnitude control.
      
      Since the output path for haptics is routed through the CODEC audio routing
      it is modelled as a signal generator within ASoC, the haptics driver calls
      DAPM to start and stop the output drivers. An appropriate output path must
      be configured via ALSA to connect the haptics source to the correct output.
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      9dd555e2
  6. 10 11月, 2012 1 次提交
  7. 30 10月, 2012 1 次提交
  8. 25 7月, 2012 1 次提交
  9. 17 3月, 2012 1 次提交
  10. 05 3月, 2012 1 次提交
  11. 12 12月, 2011 1 次提交
  12. 01 12月, 2011 1 次提交
    • H
      Input: add generic GPIO-tilt driver · 3bfd5c5b
      Heiko Stübner 提交于
      There exist tilt switches that simply report their tilt-state via
      some gpios. The number and orientation of their axes can vary
      depending on the switch used and the build of the device. Also two
      or more one-axis switches could be combined to provide multi-dimensional
      orientation.
      
      One example of a device using such a switch is the family of Qisda
      ebook readers, where the switch provides information about the
      landscape / portrait orientation of the device. The example in
      Documentation/input/gpio-tilt.txt documents exactly this one-axis
      device.
      Signed-off-by: NHeiko Stuebner <heiko@sntech.de>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      3bfd5c5b
  13. 24 10月, 2011 1 次提交
  14. 22 9月, 2011 1 次提交
  15. 09 8月, 2011 1 次提交
  16. 03 8月, 2011 1 次提交
  17. 07 7月, 2011 1 次提交
  18. 05 7月, 2011 1 次提交
  19. 29 6月, 2011 1 次提交
  20. 22 6月, 2011 1 次提交
  21. 27 5月, 2011 1 次提交
  22. 17 3月, 2011 1 次提交
  23. 29 12月, 2010 1 次提交
  24. 01 12月, 2010 1 次提交
  25. 06 9月, 2010 1 次提交
  26. 14 7月, 2010 1 次提交
  27. 25 6月, 2010 1 次提交
  28. 22 5月, 2010 1 次提交
  29. 14 4月, 2010 2 次提交
  30. 09 3月, 2010 1 次提交
  31. 08 3月, 2010 1 次提交
  32. 22 9月, 2009 1 次提交
  33. 17 9月, 2009 2 次提交
  34. 23 7月, 2009 1 次提交
  35. 24 4月, 2009 1 次提交
    • D
      Input: add dm355evm_keys driver · eb990b55
      David Brownell 提交于
      Simple input driver support for the events reported by the
      MSP430 firmware on the DM355 EVM.  Verified using the RC5
      remote included with the kit; docs weren't quite right.
      
      Some of the keycode selections might need improvement; they
      can be remapped, so there's at least a runtime workaround.
      (I also suspect Linux may someday merit more generic support
      for RC5 based remote controls.)
      
      These events don't distinguish key press vs release events,
      so this reports both and then skips the next event if it's
      identical.  The RC5 remote codes include a "toggle" bit that
      can help detect autorepeated keys; but this driver doesn't
      bother with those nuances.
      
      This driver relies on the drivers/mfd/dm355evm_msp.c code
      for core features, including sharing I2C access to this
      firmware with GPIO, LED, and RTC support.
      
      [dtor@mail.ru: fix error unwindng path in probe()]
      Signed-off-by: NDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NKevin Hilman <khilman@deeprootsystems.com>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      eb990b55
  36. 20 4月, 2009 1 次提交
  37. 10 3月, 2009 2 次提交
    • D
      Input: arrange drivers/input/misc/Makefile in alphabetical order · 74f733c7
      Dmitry Torokhov 提交于
      Everyone adds their driver to the end of the list, hopefully if it is
      in alphabetical order new drivers will spread out a bit and I can merge
      them more easily.
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      74f733c7
    • P
      Input: add driver for S1 button of rb532 · d9bdffd2
      Phil Sutter 提交于
      Mikrotik's Routerboard 532 has two builtin buttons, from which one
      triggers a hardware reset. The other one is accessible through GPIO
      pin 1. Sadly, this pin is being multiplexed with UART0 input, so
      enabling it as interrupt source (as implied by the gpio-keys driver)
      is not possible unless UART0 has been turned off. The later one though
      is a rather bad idea as the Routerboard is an embedded device with
      only a single serial port, so it's almost always used as serial
      console device.
      
      This patch adds a driver based on INPUT_POLLDEV, which disables the
      UART and reconfigures GPIO pin 1 temporarily while reading the button
      state.  This procedure works fine and has been tested as part of
      another, unpublished driver for this device.
      Signed-off-by: NPhil Sutter <n0-1@freewrt.org>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      d9bdffd2