Skip to content

GitLab

Switch branch/tag
  1. 30 Aug, 2016 1 commit
    • Vignesh R's avatar
      Input: add generic input driver to read encoded GPIO lines · 69464161
      Vignesh R authored 
      
Add a driver to read group of GPIO lines and provide its status as a
numerical value as input event to the system. This will help in
interfacing devices, that can be connected over GPIOs, that provide
input to the system by driving GPIO lines connected to them like a
rotary dial or a switch.

For example, a rotary switch can be connected to four GPIO lines. The
status of the GPIO lines reflect the actual position of the rotary
switch dial. For example, if dial points to 9, then the four GPIO lines
connected to the switch will read HLLH(0b'1001 = 9). This value
can be reported as an ABS_* event to the input subsystem.
Signed-off-by: default avatarVignesh R <vigneshr@ti.com>
Acked-by: default avatarRob Herring <robh@kernel.org>
Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      69464161
  3. 23 Jun, 2016 1 commit
  5. 19 May, 2016 1 commit
  7. 18 May, 2016 1 commit
  9. 27 Jan, 2016 1 commit
    • Arnd Bergmann's avatar
      Input: sirfsoc-onkey - allow modular build · af6e9463
      Arnd Bergmann authored 
      
CONFIG_INPUT may itself be a loadable module, but the sirf power key
driver is listed as 'bool', which makes it possible to select
a broken configuration with the driver built-in but the subsystem
not loaded. In this configuration, we get a link error:

drivers/input/built-in.o: In function `sirfsoc_pwrc_isr':
drivers/input/misc/sirfsoc-onkey.c:63: undefined reference to `input_event'
drivers/input/built-in.o: In function `sirfsoc_pwrc_isr':
include/linux/input.h:414: undefined reference to `input_event'
drivers/input/built-in.o: In function `sirfsoc_pwrc_probe':
drivers/input/misc/sirfsoc-onkey.c:132: undefined reference to `devm_input_allocate_device'
drivers/input/misc/sirfsoc-onkey.c:139: undefined reference to `input_set_capability'
drivers/input/misc/sirfsoc-onkey.c:161: undefined reference to `input_register_device'
drivers/input/built-in.o: In function `sirfsoc_pwrc_report_event':
drivers/input/misc/sirfsoc-onkey.c:48: undefined reference to `input_event'
drivers/input/built-in.o: In function `sirfsoc_pwrc_report_event':
include/linux/input.h:414: undefined reference to `input_event'
drivers/input/built-in.o:(.debug_addr+0x24): undefined reference to `input_event'
drivers/input/built-in.o:(.debug_addr+0xbc): undefined reference to `devm_input_allocate_device'
drivers/input/built-in.o:(.debug_addr+0x104): undefined reference to `input_set_capability'
drivers/input/built-in.o:(.debug_addr+0x128): undefined reference to `input_register_device'

This marks the driver as 'tristate' so it becomes possible to have
it in a loadable module, mainly to help with randconfig builds.

We also have to add a missing semicolon here, which ended up not
being needed in built-in mode because the following MODULE_DEVICE_TABLE
is an empty macro followed by another semicolon then.
Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      af6e9463
  11. 26 Oct, 2015 1 commit
  13. 29 Sep, 2015 1 commit
    • S Twiss's avatar
      Input: add DA9062 OnKey capability to DA9063 OnKey driver · a27b5e0a
      S Twiss authored 
      
Add DA9062 OnKey support into the existing DA9063 OnKey driver component by
using generic access tables for common register and bit mask definitions.

The following change will add generic register and bit mask support to the
DA9063 OnKey.

The following alterations have been made to the DA9063 OnKey:

- Addition of a da906x_chip_config structure to hold all
  generic registers and bitmasks for this type of OnKey component.
- Addition of an struct of_device_id table for DA9063 and DA9062
  defaults
- Refactoring functions to use struct da9063_onkey accesses to generic
  registers/masks instead of using defines from registers.h
- Re-work of da9063_onkey_probe() to use of_match_node() and
  dev_get_regmap() to provide initialisation of generic registers and
  masks and access to regmap
Signed-off-by: default avatarSteve Twiss <stwiss.opensource@diasemi.com>
Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      a27b5e0a
  15. 07 Aug, 2015 2 commits
  17. 04 Aug, 2015 1 commit
  19. 09 Jun, 2015 1 commit
  21. 08 May, 2015 2 commits
  23. 21 Mar, 2015 1 commit
  25. 06 Mar, 2015 1 commit
  27. 10 Jan, 2015 1 commit
  29. 08 Jan, 2015 1 commit
  31. 28 Dec, 2014 1 commit
  33. 22 Dec, 2014 1 commit
  35. 12 Sep, 2014 2 commits
    • Jaewon Kim's avatar
      Input: add haptic driver on max77693 · a3b3ca75
      Jaewon Kim authored 
      
This driver to supports the haptic controller on MAX77693 Multifunction
device with PMIC, CHARGER, LED, MUIC, HAPTIC.

This driver supports external pwm and LRA (Linear Resonant Actuator) motor.
User can control the haptic device via force feedback framework.
Signed-off-by: default avatarJaewon Kim <jaewon02.kim@samsung.com>
Acked-by: default avatarChanwoo Choi <cw00.choi@samsung.com>
Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      a3b3ca75
    • Nishanth Menon's avatar
      Input: introduce palmas-pwrbutton · adff5962
      Nishanth Menon authored 
      
Many palmas family of PMICs have support for interrupt based power button.
This allows the device to notify the processor of external push button
events over the shared palmas interrupt. However, this event is generated
only during a "press" operation. Software is supposed to poll(sigh!) for
detecting a release event.

The PMIC also supports ability to power off independent of the software
decisions when the button is pressed for a long duration if the PMIC is
appropriately configured on the platform.

Even though the function is similar to twl4030_pwrbutton, it is
substantially different in operation to belong to a new driver of it's own.

Based on original work done by Girish S Ghongdemath <girishsg@ti.com>
Signed-off-by: default avatarNishanth Menon <nm@ti.com>
Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      adff5962
  37. 08 Sep, 2014 1 commit
  39. 20 Aug, 2014 1 commit
  41. 14 May, 2014 1 commit
  43. 31 Mar, 2014 1 commit
  45. 24 Mar, 2014 1 commit
  47. 10 Feb, 2014 1 commit
    • Sascha Hauer's avatar
      pwm: Remove obsolete HAVE_PWM Kconfig symbol · 557fe99d
      Sascha Hauer authored 
      
Before we had the PWM framework we used to have a barebone PWM api. The
HAVE_PWM Kconfig symbol used to be selected by the PWM drivers to specify
the PWM API is present in the kernel. Since the last legacy driver is gone
the HAVE_PWM symbol can go aswell.
Signed-off-by: default avatarSascha Hauer <s.hauer@pengutronix.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Eric Miao <eric.y.miao@gmail.com>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
Cc: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pwm@vger.kernel.orig
Cc: Russell King <linux@arm.linux.org.uk>
Cc: Ralf Baechle <ralf@linux-mips.org>
Signed-off-by: default avatarThierry Reding <thierry.reding@gmail.com>
      557fe99d
  49. 21 Jan, 2014 1 commit
  51. 26 Nov, 2013 1 commit
  53. 22 Oct, 2013 1 commit
    • Majunath Goudar's avatar
      Input: fix PWM-related undefined reference errors · 33777f34
      Majunath Goudar authored 
      
This patch adds a PWM dependency to configure the INPUT_MAX8997_HAPTIC
and INPUT_PWM_BEEPER. Without this patch, build system can lead to build
failure. This was observed during randconfig testing, in which
INPUT_MAX8997_HAPTIC or INPUT_PWM_BEEPER was enabled w/o PWM being
enabled, leading to the following errors:

init/built-in.o
drivers/built-in.o: In function `max8997_haptic_disable':
:(.text+0x1073a0): undefined reference to `pwm_disable'
drivers/built-in.o: In function `max8997_haptic_remove':
:(.text+0x1073fc): undefined reference to `pwm_free'
drivers/built-in.o: In function `max8997_haptic_play_effect_work':
:(.text+0x1074f0): undefined reference to `pwm_config'
:(.text+0x1075b0): undefined reference to `pwm_enable'
drivers/built-in.o: In function `max8997_haptic_probe':
:(.text+0x1076f8): undefined reference to `pwm_request'
:(.text+0x1077e8): undefined reference to `pwm_free'
drivers/built-in.o: In function `pwm_beeper_resume':
:(.text+0x1081a4): undefined reference to `pwm_config'
make: *** [vmlinux] Error 1
Signed-off-by: default avatarManjunath Goudar <csmanjuvijay@gmail.com>
Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      33777f34
  55. 26 Aug, 2013 1 commit
  57. 03 Jun, 2013 1 commit
  59. 16 Apr, 2013 1 commit
  61. 12 Mar, 2013 1 commit
    • Dmitry Torokhov's avatar
      Input: add IMS Passenger Control Unit driver · 628329d5
      Dmitry Torokhov authored 
      
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: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      628329d5
  63. 28 Nov, 2012 1 commit
    • Mark Brown's avatar
      Input - arizona-haptics: Add driver haptics module on Arizona CODECs · 9dd555e2
      Mark Brown authored 
      
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: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      9dd555e2
  65. 10 Nov, 2012 1 commit
  67. 03 Nov, 2012 1 commit
  69. 30 Oct, 2012 1 commit
  71. 25 Oct, 2012 1 commit
  73. 24 Jul, 2012 1 commit
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7