Skip to content
Snippets Groups Projects
  1. Jul 06, 2011
  2. Jul 04, 2011
  3. Jun 29, 2011
  4. Jun 22, 2011
  5. May 26, 2011
  6. Mar 17, 2011
  7. Dec 29, 2010
  8. Dec 01, 2010
  9. Sep 05, 2010
  10. Jul 14, 2010
  11. Jun 25, 2010
  12. May 22, 2010
  13. Apr 14, 2010
  14. Mar 09, 2010
  15. Mar 07, 2010
  16. Dec 07, 2009
  17. Nov 02, 2009
  18. Sep 24, 2009
    • Ingo Molnar's avatar
      input: fix build failures caused by Kconfig Winbond WPCD376I Consumer IR... · d2b5ec3a
      Ingo Molnar authored
      input: fix build failures caused by Kconfig Winbond WPCD376I Consumer IR hardware driver Kconfig entry
      
      Fix these warnings:
      
        drivers/built-in.o: In function `apanel_remove':
        apanel.c:(.text+0x56e852): undefined reference to `led_classdev_unregister'
        drivers/built-in.o: In function `apanel_probe':
        apanel.c:(.text+0x56eae3): undefined reference to `led_classdev_register'
        drivers/built-in.o: In function `acpi_fujitsu_hotkey_add':
        fujitsu-laptop.c:(.text+0x5d7647): undefined reference to `led_classdev_register'
        fujitsu-laptop.c:(.text+0x5d76b5): undefined reference to `led_classdev_register'
        drivers/built-in.o: In function `wbcir_probe':
        winbond-cir.c:(.devinit.text+0x5f375): undefined reference to `led_classdev_register'
        winbond-cir.c:(.devinit.text+0x5f663): undefined reference to `led_classdev_unregister'
        drivers/built-in.o: In function `wbcir_remove':
        winbond-cir.c:(.devexit.text+0x7f23): undefined reference to `led_classdev_unregister'
        drivers/built-in.o: In function `fujitsu_cleanup':
        fujitsu-laptop.c:(.exit.text+0xbe37): undefined reference to `led_classdev_unregister'
        fujitsu-laptop.c:(.exit.text+0xbe53): undefined reference to `led_classdev_unregister'
      
      It happens because the new INPUT_WINBOND_CIR driver relies on new-leds
      infrastructure - but does not select it in drivers/input/misc/Kconfig.
      But it selects LEDS_CLASS, which confuses a number of other drivers into
      thinking that all the leds infrastructure is in place.
      
      Fix this by selecting NEW_LEDS as well, like similar drivers do.
      
      Eventually, this whole leds infrastructure complexity should be
      cleaned up, it's been going on for years.
      
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
      Cc: Dmitry Torokhov <dtor@mail.ru>
      Cc: David Härdeman <david@hardeman.nu>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      d2b5ec3a
  19. Sep 22, 2009
  20. Sep 17, 2009
  21. Jul 23, 2009
  22. Jun 12, 2009
  23. Apr 23, 2009
    • David Brownell's avatar
      Input: add dm355evm_keys driver · eb990b55
      David Brownell authored
      
      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: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarKevin Hilman <khilman@deeprootsystems.com>
      Signed-off-by: default avatarDmitry Torokhov <dtor@mail.ru>
      eb990b55
  24. Apr 20, 2009
  25. Apr 15, 2009
  26. Mar 09, 2009
    • Phil Sutter's avatar
      Input: add driver for S1 button of rb532 · d9bdffd2
      Phil Sutter authored
      
      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: default avatarPhil Sutter <n0-1@freewrt.org>
      Signed-off-by: default avatarDmitry Torokhov <dtor@mail.ru>
      d9bdffd2
  27. Mar 08, 2009
  28. Jan 10, 2009
  29. Aug 08, 2008
  30. Jul 18, 2008
  31. Jul 07, 2008
  32. Jun 05, 2008
  33. May 07, 2008
  34. Apr 24, 2008
  35. Mar 04, 2008
Loading