1. 04 Jun, 2018 1 commit
  2. 26 Mar, 2018 1 commit
  3. 08 Mar, 2018 1 commit
  4. 02 Jan, 2018 1 commit
    • Linus Walleij's avatar
      Input: gpio_tilt - delete driver · 3c8a23c2
      Linus Walleij authored
      This driver was merged in 2011 as a tool for detecting the orientation
      of a screen. The device driver assumes board file setup using the
      platform data from <linux/input/gpio_tilt.h>. But no boards in the
      kernel tree defines this platform data.
      As I am faced with refactoring drivers to use GPIO descriptors and
      pass decriptor tables from boards, or use the device tree device
      drivers like these creates a serious problem: I cannot fix them and
      cannot test them, not even compile-test them with a system actually
      using it (no in-tree boardfile).
      I suggest to delete this driver and rewrite it using device tree if
      it is still in use on actively maintained systems.
      I can also offer to rewrite it out of the blue using device tree if
      someone promise to test it and help me iterate it.
      Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Acked-by: default avatarHeiko Stuebner <heiko@sntech.de>
      Patchwork-Id: 10133609
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
  5. 02 Nov, 2017 1 commit
    • Greg Kroah-Hartman's avatar
      License cleanup: add SPDX GPL-2.0 license identifier to files with no license · b2441318
      Greg Kroah-Hartman authored
      Many source files in the tree are missing licensing information, which
      makes it harder for compliance tools to determine the correct license.
      By default all files without license information are under the default
      license of the kernel, which is GPL version 2.
      Update the files which contain no license information with the 'GPL-2.0'
      SPDX license identifier.  The SPDX identifier is a legally binding
      shorthand, which can be used instead of the full boiler plate text.
      This patch is based on work done by Thomas Gleixner and Kate Stewart and
      Philippe Ombredanne.
      How this work was done:
      Patches were generated and checked against linux-4.14-rc6 for a subset of
      the use cases:
       - file had no licensing information it it.
       - file was a */uapi/* one with no licensing information in it,
       - file was a */uapi/* one with existing licensing information,
      Further patches will be generated in subsequent months to fix up cases
      where non-standard license headers were used, and references to license
      had to be inferred by heuristics based on keywords.
      The analysis to determine which SPDX License Identifier to be applied to
      a file was done in a spreadsheet of side by side results from of the
      output of two independent scanners (ScanCode & Windriver) producing SPDX
      tag:value files created by Philippe Ombredanne.  Philippe prepared the
      base worksheet, and did an initial spot review of a few 1000 files.
      The 4.13 kernel was the starting point of the analysis with 60,537 files
      assessed.  Kate Stewart did a file by file comparison of the scanner
      results in the spreadsheet to determine which SPDX license identifier(s)
      to be applied to the file. She confirmed any determination that was not
      immediately clear with lawyers working with the Linux Foundation.
      Criteria used to select files for SPDX license identifier tagging was:
       - Files considered eligible had to be source code files.
       - Make and config files were included as candidates if they contained >5
         lines of source
       - File already had some variant of a license header in it (even if <5
      All documentation files were explicitly excluded.
      The following heuristics were used to determine which SPDX license
      identifiers to apply.
       - when both scanners couldn't find any license traces, file was
         considered to have no license information in it, and the top level
         COPYING file license applied.
         For non */uapi/* files that summary was:
         SPDX license identifier                            # files
         GPL-2.0                                              11139
         and resulted in the first patch in this series.
         If that file was a */uapi/* path one, it was "GPL-2.0 WITH
         Linux-syscall-note" otherwise it was "GPL-2.0".  Results of that was:
         SPDX license identifier                            # files
         GPL-2.0 WITH Linux-syscall-note                        930
         and resulted in the second patch in this series.
       - if a file had some form of licensing information in it, and was one
         of the */uapi/* ones, it was denoted with the Linux-syscall-note if
         any GPL family license was found in the file or had no licensing in
         it (per prior point).  Results summary:
         SPDX license identifier                            # files
         GPL-2.0 WITH Linux-syscall-note                       270
         GPL-2.0+ WITH Linux-syscall-note                      169
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21
         ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17
         LGPL-2.1+ WITH Linux-syscall-note                      15
         GPL-1.0+ WITH Linux-syscall-note                       14
         ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5
         LGPL-2.0+ WITH Linux-syscall-note                       4
         LGPL-2.1 WITH Linux-syscall-note                        3
         ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3
         ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1
         and that resulted in the third patch in this series.
       - when the two scanners agreed on the detected license(s), that became
         the concluded license(s).
       - when there was disagreement between the two scanners (one detected a
         license but the other didn't, or they both detected different
         licenses) a manual inspection of the file occurred.
       - In most cases a manual inspection of the information in the file
         resulted in a clear resolution of the license that should apply (and
         which scanner probably needed to revisit its heuristics).
       - When it was not immediately clear, the license identifier was
         confirmed with lawyers working with the Linux Foundation.
       - If there was any question as to the appropriate license identifier,
         the file was flagged for further research and to be revisited later
         in time.
      In total, over 70 hours of logged manual review was done on the
      spreadsheet to determine the SPDX license identifiers to apply to the
      source files by Kate, Philippe, Thomas and, in some cases, confirmation
      by lawyers working with the Linux Foundation.
      Kate also obtained a third independent scan of the 4.13 code base from
      FOSSology, and compared selected files where the other two scanners
      disagreed against that SPDX file, to see if there was new insights.  The
      Windriver scanner is based on an older version of FOSSology in part, so
      they are related.
      Thomas did random spot checks in about 500 files from the spreadsheets
      for the uapi headers and agreed with SPDX license identifier in the
      files he inspected. For the non-uapi files Thomas did random spot checks
      in about 15000 files.
      In initial set of patches against 4.14-rc6, 3 files were found to have
      copy/paste license identifier errors, and have been fixed to reflect the
      correct identifier.
      Additionally Philippe spent 10 hours this week doing a detailed manual
      inspection and review of the 12,461 patched files from the initial patch
      version early this week with:
       - a full scancode scan run, collecting the matched texts, detected
         license ids and scores
       - reviewing anything where there was a license detected (about 500+
         files) to ensure that the applied SPDX license was correct
       - reviewing anything where there was no detection but the patch license
         was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied
         SPDX license was correct
      This produced a worksheet with 20 files needing minor correction.  This
      worksheet was then exported into 3 different .csv files for the
      different types of files to be modified.
      These .csv files were then reviewed by Greg.  Thomas wrote a script to
      parse the csv files and add the proper SPDX tag to the file, in the
      format that the file expected.  This script was further refined by Greg
      based on the output to detect more types of files automatically and to
      distinguish between header and source .c files (which need different
      comment types.)  Finally Greg ran the script using the .csv files to
      generate the patches.
      Reviewed-by: default avatarKate Stewart <kstewart@linuxfoundation.org>
      Reviewed-by: default avatarPhilippe Ombredanne <pombredanne@nexb.com>
      Reviewed-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
  6. 04 Sep, 2017 1 commit
  7. 25 Jul, 2017 1 commit
  8. 11 Apr, 2017 1 commit
  9. 31 Jan, 2017 1 commit
  10. 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>
  11. 23 Jun, 2016 1 commit
  12. 18 May, 2016 1 commit
  13. 07 Aug, 2015 1 commit
  14. 09 Jun, 2015 1 commit
  15. 08 May, 2015 1 commit
  16. 21 Mar, 2015 1 commit
  17. 06 Mar, 2015 1 commit
  18. 10 Jan, 2015 1 commit
  19. 08 Jan, 2015 1 commit
  20. 28 Dec, 2014 1 commit
  21. 22 Dec, 2014 1 commit
  22. 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>
    • 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>
  23. 08 Sep, 2014 1 commit
  24. 20 Aug, 2014 1 commit
  25. 31 Mar, 2014 1 commit
  26. 26 Nov, 2013 1 commit
  27. 26 Aug, 2013 1 commit
  28. 03 Jun, 2013 1 commit
  29. 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>
  30. 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>
  31. 10 Nov, 2012 1 commit
  32. 30 Oct, 2012 1 commit
  33. 24 Jul, 2012 1 commit
  34. 17 Mar, 2012 1 commit
  35. 04 Mar, 2012 1 commit
  36. 12 Dec, 2011 1 commit
  37. 01 Dec, 2011 1 commit
    • Heiko Stübner's avatar
      Input: add generic GPIO-tilt driver · 3bfd5c5b
      Heiko Stübner authored
      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
      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
      Signed-off-by: default avatarHeiko Stuebner <heiko@sntech.de>
      Signed-off-by: default avatarDmitry Torokhov <dtor@mail.ru>
  38. 24 Oct, 2011 1 commit
  39. 22 Sep, 2011 1 commit