1. 12 7月, 2015 2 次提交
  2. 26 6月, 2015 1 次提交
  3. 02 2月, 2015 1 次提交
  4. 08 8月, 2014 1 次提交
  5. 29 7月, 2014 1 次提交
  6. 29 5月, 2014 1 次提交
  7. 19 5月, 2014 2 次提交
  8. 31 3月, 2014 2 次提交
  9. 26 6月, 2013 1 次提交
  10. 13 6月, 2013 2 次提交
  11. 08 4月, 2013 1 次提交
  12. 05 4月, 2013 1 次提交
    • S
      input: matrix-keymap: Add function to read the new DT binding · 43840415
      Simon Glass 提交于
      We now have a binding which adds two parameters to the matrix keypad DT
      node. This is separate from the GPIO-driven matrix keypad binding, and
      unfortunately incompatible, since that uses row-gpios/col-gpios for the
      row and column counts.
      
      So the easiest option here is to provide a function for non-GPIO drivers
      to use to decode the binding.
      
      Note: We could in fact create an entirely separate structure to hold
      these two fields, but it does not seem worth it, yet. If we have more
      parameters then we can add this, and then refactor each driver to hold
      such a structure.
      Signed-off-by: NSimon Glass <sjg@chromium.org>
      Acked-by: NDmitry Torokhov <dmitry.torokhov@gmail.com>
      Tested-by: Sourav Poddar <sourav.poddar@ti.com> (v2)
      Signed-off-by: NSamuel Ortiz <sameo@linux.intel.com>
      43840415
  13. 25 2月, 2013 1 次提交
  14. 16 2月, 2013 1 次提交
  15. 25 12月, 2012 1 次提交
  16. 28 11月, 2012 1 次提交
  17. 15 11月, 2012 1 次提交
  18. 06 11月, 2012 2 次提交
  19. 20 9月, 2012 5 次提交
  20. 05 9月, 2012 1 次提交
  21. 09 8月, 2012 1 次提交
    • A
      Input: eeti_ts: pass gpio value instead of IRQ · 4eef6cbf
      Arnd Bergmann 提交于
      The EETI touchscreen asserts its IRQ line as soon as it has data in its
      internal buffers. The line is automatically deasserted once all data has
      been read via I2C. Hence, the driver has to monitor the GPIO line and
      cannot simply rely on the interrupt handler reception.
      
      In the current implementation of the driver, irq_to_gpio() is used to
      determine the GPIO number from the i2c_client's IRQ value.
      
      As irq_to_gpio() is not available on all platforms, this patch changes
      this and makes the driver ignore the passed in IRQ. Instead, a GPIO is
      added to the platform_data struct and gpio_to_irq is used to derive the
      IRQ from that GPIO. If this fails, bail out. The driver is only able to
      work in environments where the touchscreen GPIO can be mapped to an
      IRQ.
      
      Without this patch, building raumfeld_defconfig results in:
      
      drivers/input/touchscreen/eeti_ts.c: In function 'eeti_ts_irq_active':
      drivers/input/touchscreen/eeti_ts.c:65:2: error: implicit declaration of function 'irq_to_gpio' [-Werror=implicit-function-declaration]
      Signed-off-by: NDaniel Mack <zonque@gmail.com>
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Cc: stable@vger.kernel.org (v3.2+)
      Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
      Cc: Sven Neumann <s.neumann@raumfeld.com>
      Cc: linux-input@vger.kernel.org
      Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
      4eef6cbf
  22. 25 7月, 2012 1 次提交
  23. 11 5月, 2012 3 次提交
  24. 05 4月, 2012 1 次提交
  25. 18 3月, 2012 1 次提交
  26. 17 3月, 2012 1 次提交
  27. 14 3月, 2012 1 次提交
  28. 05 3月, 2012 1 次提交
  29. 02 2月, 2012 1 次提交
反馈
建议
客服 返回
顶部