1. 04 12月, 2009 1 次提交
  2. 06 10月, 2009 1 次提交
  3. 23 9月, 2009 1 次提交
  4. 18 9月, 2009 2 次提交
  5. 17 9月, 2009 1 次提交
  6. 05 9月, 2009 1 次提交
  7. 04 9月, 2009 1 次提交
  8. 02 9月, 2009 1 次提交
  9. 21 8月, 2009 2 次提交
  10. 12 8月, 2009 1 次提交
  11. 05 8月, 2009 3 次提交
  12. 28 7月, 2009 1 次提交
  13. 27 7月, 2009 4 次提交
  14. 21 7月, 2009 2 次提交
  15. 13 7月, 2009 2 次提交
  16. 08 7月, 2009 2 次提交
  17. 16 6月, 2009 1 次提交
    • G
      input: remove driver_data direct access of struct device · 017596b6
      Greg Kroah-Hartman 提交于
      In the near future, the driver core is going to not allow direct access
      to the driver_data pointer in struct device.  Instead, the functions
      dev_get_drvdata() and dev_set_drvdata() should be used.  These functions
      have been around since the beginning, so are backwards compatible with
      all older kernel versions.
      
      Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
      Cc: linux-input@vger.kernel.org
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      017596b6
  18. 11 6月, 2009 2 次提交
  19. 27 5月, 2009 1 次提交
  20. 20 5月, 2009 3 次提交
  21. 16 5月, 2009 1 次提交
  22. 12 5月, 2009 1 次提交
  23. 01 5月, 2009 1 次提交
  24. 19 4月, 2009 1 次提交
  25. 18 4月, 2009 2 次提交
  26. 16 4月, 2009 1 次提交
    • B
      Input: ads7846 - fix unsafe disable_irq · 3f3e7c6e
      Ben Nizette 提交于
      The use of disable_irq inside the handler for the interrupt being
      disabled has always been dangerous.  disable_irq should wait for that
      handler to complete before returning -> deadlock.
      
      For some reason this wasn't actually the case until 3aa551c9 was merged
      but since this time, the ads7846 driver has deadlocked the system on
      first interrupt.
      
      Convert the driver to use the handler-safe _nosync variant.
      Signed-off-by: NBen Nizette <bn@niasdigital.com>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      3f3e7c6e