1. 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
  2. 11 6月, 2009 2 次提交
  3. 27 5月, 2009 1 次提交
  4. 20 5月, 2009 3 次提交
  5. 16 5月, 2009 1 次提交
  6. 12 5月, 2009 1 次提交
  7. 01 5月, 2009 1 次提交
  8. 19 4月, 2009 1 次提交
  9. 18 4月, 2009 2 次提交
  10. 16 4月, 2009 2 次提交
  11. 15 4月, 2009 3 次提交
  12. 12 4月, 2009 2 次提交
  13. 02 4月, 2009 1 次提交
  14. 30 3月, 2009 1 次提交
  15. 10 3月, 2009 2 次提交
  16. 09 3月, 2009 5 次提交
  17. 01 3月, 2009 1 次提交
  18. 30 1月, 2009 1 次提交
  19. 13 1月, 2009 1 次提交
    • U
      Input: corgi_ts - mark probe function as __devinit · 840207ed
      Uwe Kleine-König 提交于
      A pointer to corgits_probe is passed to the core via
      platform_driver_register and so the function must not disappear when the
      .init sections are discarded.  Otherwise (if also having HOTPLUG=y)
      unbinding and binding a device to the driver via sysfs will result in an
      oops as does a device being registered late.
      
      An alternative to this patch is using platform_driver_probe instead of
      platform_driver_register plus removing the pointer to the probe function
      from the struct platform_driver.
      
      [dtor@mail.ru: fixed some more section markups]
      Signed-off-by: NUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      840207ed
  20. 11 1月, 2009 1 次提交
  21. 08 1月, 2009 1 次提交
  22. 23 12月, 2008 2 次提交
  23. 20 12月, 2008 1 次提交
  24. 02 12月, 2008 1 次提交
  25. 25 11月, 2008 2 次提交
    • P
      hrtimer: removing all ur callback modes · ca109491
      Peter Zijlstra 提交于
      Impact: cleanup, move all hrtimer processing into hardirq context
      
      This is an attempt at removing some of the hrtimer complexity by
      reducing the number of callback modes to 1.
      
      This means that all hrtimer callback functions will be ran from HARD-irq
      context.
      
      I went through all the 30 odd hrtimer callback functions in the kernel
      and saw only one that I'm not quite sure of, which is the one in
      net/can/bcm.c - hence I'm CC-ing the folks responsible for that code.
      
      Furthermore, the hrtimer core now calls callbacks directly with IRQs
      disabled in case you try to enqueue an expired timer. If this timer is a
      periodic timer (which should use hrtimer_forward() to advance its time)
      then it might be possible to end up in an inf. recursive loop due to the
      fact that hrtimer_forward() doesn't round up to the next timer
      granularity, and therefore keeps on calling the callback - obviously
      this needs a fix.
      
      Aside from that, this seems to compile and actually boot on my dual core
      test box - although I'm sure there are some bugs in, me not hitting any
      makes me certain :-)
      Signed-off-by: NPeter Zijlstra <a.p.zijlstra@chello.nl>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      ca109491
    • J
      Input: add support for Wacom W8001 penabled serial touchscreen · 3eb1aa43
      Jaya Kumar 提交于
      The Wacom W8001 sensor is a sensor device (uses electromagnetic
      resonance) and it is interfaced via its serial microcontroller
      to the host.
      Signed-off-by: NJaya Kumar <jayakumar.lkml@gmail.com>
      Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      3eb1aa43