1. 13 Nov, 2015 1 commit
  2. 09 Nov, 2015 1 commit
  3. 06 Nov, 2015 1 commit
  4. 05 Nov, 2015 2 commits
  5. 03 Nov, 2015 4 commits
  6. 31 Oct, 2015 1 commit
  7. 28 Oct, 2015 1 commit
    • Stephen Chandler Paul's avatar
      Input: add userio module · 5523662e
      Stephen Chandler Paul authored
      
      
      Debugging input devices, specifically laptop touchpads, can be tricky
      without having the physical device handy. Here we try to remedy that
      with userio. This module allows an application to connect to a character
      device provided by the kernel, and emulate any serio device. In
      combination with userspace programs that can record PS/2 devices and
      replay them through the /dev/userio device, this allows developers to
      debug driver issues on the PS/2 level with devices simply by requesting
      a recording from the user experiencing the issue without having to have
      the physical hardware in front of them.
      Signed-off-by: default avatarStephen Chandler Paul <cpaul@redhat.com>
      Reviewed-by: default avatarDavid Herrmann <dh.herrmann@gmail.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      5523662e
  8. 27 Oct, 2015 3 commits
    • David Herrmann's avatar
      Input: evdev - add event-mask API · 06a16293
      David Herrmann authored
      
      
      Hardware manufacturers group keys in the weirdest way possible. This may
      cause a power-key to be grouped together with normal keyboard keys and
      thus be reported on the same kernel interface.
      
      However, user-space is often only interested in specific sets of events.
      For instance, daemons dealing with system-reboot (like systemd-logind)
      listen for KEY_POWER, but are not interested in any main keyboard keys.
      Usually, power keys are reported via separate interfaces, however,
      some i8042 boards report it in the AT matrix. To avoid waking up those
      system daemons on each key-press, we had two ideas:
       - split off KEY_POWER into a separate interface unconditionally
       - allow filtering a specific set of events on evdev FDs
      
      Splitting of KEY_POWER is a rather weird way to deal with this and may
      break backwards-compatibility. It is also specific to KEY_POWER and might
      be required for other stuff, too. Moreover, we might end up with a huge
      set of input-devices just to have them properly split.
      
      Hence, this patchset implements the second idea: An event-mask to specify
      which events you're interested in. Two ioctls allow setting this mask for
      each event-type. If not set, all events are reported. The type==0 entry is
      used same as in EVIOCGBIT to set the actual EV_* mask of filtered events.
      This way, you have a two-level filter.
      
      We are heavily forward-compatible to new event-types and event-codes. So
      new user-space will be able to run on an old kernel which doesn't know the
      given event-codes or event-types.
      Signed-off-by: default avatarDavid Herrmann <dh.herrmann@gmail.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      06a16293
    • Javier Martinez Canillas's avatar
      Input: snvs_pwrkey - remove duplicated semicolon · 9ace41ad
      Javier Martinez Canillas authored
      
      
      Remove the unneded semicolon since it is clearly a typo error.
      Signed-off-by: default avatarJavier Martinez Canillas <javier@osg.samsung.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      9ace41ad
    • Hans de Goede's avatar
      Input: alps - only the Dell Latitude D420/430/620/630 have separate stick button bits · 19556219
      Hans de Goede authored
      commit 92bac83d
      
       ("Input: alps - non interleaved V2 dualpoint has
      separate stick button bits") assumes that all alps v2 non-interleaved
      dual point setups have the separate stick button bits.
      
      Later we limited this to Dell laptops only because of reports that this
      broke things on non Dell laptops. Now it turns out that this breaks things
      on the Dell Latitude D600 too. So it seems that only the Dell Latitude
      D420/430/620/630, which all share the same touchpad / stick combo,
      have these separate bits.
      
      This patch limits the checking of the separate bits to only these models
      fixing regressions with other models.
      Reported-and-tested-by: default avatarLarry Finger <Larry.Finger@lwfinger.net>
      Cc: stable@vger.kernel.org
      Tested-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Acked-By: default avatarPali Rohár <pali.rohar@gmail.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      19556219
  9. 26 Oct, 2015 4 commits
  10. 23 Oct, 2015 3 commits
  11. 19 Oct, 2015 1 commit
  12. 18 Oct, 2015 1 commit
    • Randy Dunlap's avatar
      Input: sur40 - add dependency on VIDEO_V4L2 · c8a1978e
      Randy Dunlap authored
      
      
      Fix build errors due to missing Kconfig dependency.
      
      drivers/built-in.o: In function `sur40_disconnect':
      sur40.c:(.text+0x22be6e): undefined reference to `video_unregister_device'
      sur40.c:(.text+0x22be77): undefined reference to `v4l2_device_unregister'
      drivers/built-in.o: In function `sur40_process_video':
      sur40.c:(.text+0x22c1d4): undefined reference to `v4l2_get_timestamp'
      drivers/built-in.o: In function `sur40_probe':
      sur40.c:(.text+0x22ca82): undefined reference to `v4l2_device_register'
      sur40.c:(.text+0x22cb1a): undefined reference to `v4l2_device_unregister'
      sur40.c:(.text+0x22cbf7): undefined reference to `video_device_release_empty'
      sur40.c:(.text+0x22cc53): undefined reference to `__video_register_device'
      sur40.c:(.text+0x22cc90): undefined reference to `video_unregister_device'
      drivers/built-in.o: In function `sur40_vidioc_querycap':
      sur40.c:(.text+0x22ccb0): undefined reference to `video_devdata'
      Signed-off-by: default avatarRandy Dunlap <rdunlap@infradead.org>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      c8a1978e
  13. 17 Oct, 2015 1 commit
    • Vladimir Zapolskiy's avatar
      Input: lpc32xx_ts - fix warnings caused by enabling unprepared clock · 32470060
      Vladimir Zapolskiy authored
      
      
      If common clock framework is configured, the driver generates a warning,
      which is fixed by this change:
      
          root@devkit3250:~# cat /dev/input/touchscreen0
          ------------[ cut here ]------------
          WARNING: CPU: 0 PID: 720 at drivers/clk/clk.c:727 clk_core_enable+0x2c/0xa4()
          Modules linked in: sc16is7xx snd_soc_uda1380
          CPU: 0 PID: 720 Comm: cat Not tainted 4.3.0-rc2+ #199
          Hardware name: LPC32XX SoC (Flattened Device Tree)
          Backtrace:
          [<>] (dump_backtrace) from [<>] (show_stack+0x18/0x1c)
          [<>] (show_stack) from [<>] (dump_stack+0x20/0x28)
          [<>] (dump_stack) from [<>] (warn_slowpath_common+0x90/0xb8)
          [<>] (warn_slowpath_common) from [<>] (warn_slowpath_null+0x24/0x2c)
          [<>] (warn_slowpath_null) from [<>] (clk_core_enable+0x2c/0xa4)
          [<>] (clk_core_enable) from [<>] (clk_enable+0x24/0x38)
          [<>] (clk_enable) from [<>] (lpc32xx_setup_tsc+0x18/0xa0)
          [<>] (lpc32xx_setup_tsc) from [<>] (lpc32xx_ts_open+0x14/0x1c)
          [<>] (lpc32xx_ts_open) from [<>] (input_open_device+0x74/0xb0)
          [<>] (input_open_device) from [<>] (evdev_open+0x110/0x16c)
          [<>] (evdev_open) from [<>] (chrdev_open+0x1b4/0x1dc)
          [<>] (chrdev_open) from [<>] (do_dentry_open+0x1dc/0x2f4)
          [<>] (do_dentry_open) from [<>] (vfs_open+0x6c/0x70)
          [<>] (vfs_open) from [<>] (path_openat+0xb4c/0xddc)
          [<>] (path_openat) from [<>] (do_filp_open+0x40/0x8c)
          [<>] (do_filp_open) from [<>] (do_sys_open+0x124/0x1c4)
          [<>] (do_sys_open) from [<>] (SyS_open+0x2c/0x30)
          [<>] (SyS_open) from [<>] (ret_fast_syscall+0x0/0x38)
      Signed-off-by: default avatarVladimir Zapolskiy <vz@mleia.com>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      32470060
  14. 16 Oct, 2015 10 commits
  15. 15 Oct, 2015 1 commit
    • Hans de Goede's avatar
      Input: gpio_keys_polled - add support for abs/rel axis · 6f29d3b2
      Hans de Goede authored
      
      
      This changAdd support for EV_ABS / EV_REL events to the gpio-keys-polled driver.
      
      
      The driver already allows specifying what type of events (key / rel / abs)
      a button generates when pressed, but for rel / abs axis we also need to
      specify which value this specific gpio represents.
      
      One use case is digital joysticks / direction-pads which are hooked up to
      gpio, in this case we've left and right buttons which we want to map to
      EV_ABS, ABS_X and we want generate events for left with a value of -1 and
      for right with a value of +1 (and similar for up / down and ABS_Y).
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Acked-by: default avatarRob Herring <robh@kernel.org>
      Signed-off-by: default avatarDmitry Torokhov <dmitry.torokhov@gmail.com>
      6f29d3b2
  16. 14 Oct, 2015 4 commits
  17. 10 Oct, 2015 1 commit