1. 01 9月, 2012 1 次提交
  2. 25 7月, 2012 1 次提交
  3. 18 7月, 2012 1 次提交
  4. 12 7月, 2012 1 次提交
  5. 05 7月, 2012 1 次提交
  6. 23 5月, 2012 1 次提交
  7. 21 5月, 2012 1 次提交
  8. 19 5月, 2012 1 次提交
  9. 18 5月, 2012 1 次提交
    • M
      gpio: Emma Mobile GPIO driver V2 · a07e103e
      Magnus Damm 提交于
      This patch is V2 of the Emma Mobile GPIO driver. This
      driver is designed to be reusable between multiple SoCs
      that share the same basic building block, but so far it
      has only been used on Emma Mobile EV2.
      
      Each driver instance handles 32 GPIOs with individually
      maskable IRQs. The driver operates on two I/O memory
      ranges and the 32 GPIOs are hooked up to two interrupts.
      
      In the case of Emma Mobile EV2 this GPIO building block
      is used as main external interrupt controller hooking up
      159 GPIOS as 159 interrupts via 5 driver instances and
      10 interrupts to the GIC and the Cortex-A9 Dual.
      Signed-off-by: NMagnus Damm <damm@opensource.se>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      a07e103e
  10. 12 5月, 2012 2 次提交
  11. 09 5月, 2012 2 次提交
  12. 01 5月, 2012 1 次提交
  13. 11 4月, 2012 1 次提交
  14. 08 4月, 2012 1 次提交
  15. 07 4月, 2012 1 次提交
  16. 23 3月, 2012 1 次提交
  17. 17 3月, 2012 1 次提交
  18. 04 2月, 2012 1 次提交
    • S
      gpio: Add a driver for Sodaville GPIO controller · b43ab901
      Sebastian Andrzej Siewior 提交于
      Sodaville has GPIO controller behind the PCI bus. To my suprissed it is
      not the same as on PXA.
      
      The interrupt & gpio chip can be referenced from the device tree like
      from any other driver. Unfortunately the driver which uses the gpio
      interrupt has to use irq_of_parse_and_map() instead of
      platform_get_irq(). The problem is that the platform device (which is
      created from the device tree) is most likely created before the
      interrupt chip is registered and therefore irq_of_parse_and_map() fails.
      
      In theory the driver works as module. In reality most of the irq
      functions are not exported to modules and it is possible that _this_
      module is unloaded while the provided irqs are still in use.
      Signed-off-by: NHans J. Koch <hjk@linutronix.de>
      [torbenh@linutronix.de: make it work after the irq namespace cleanup,
      	                add some device tree entries.]
      Signed-off-by: NTorben Hohn <torbenh@linutronix.de>
      [bigeasy@linutronix.de: convert to generic irq & gpio chip]
      Signed-off-by: NSebastian Andrzej Siewior <bigeasy@linutronix.de>
      [grant.likely@secretlab.ca: depend on x86 to avoid irq_domain breakage]
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      b43ab901
  19. 30 1月, 2012 1 次提交
  20. 18 1月, 2012 1 次提交
  21. 05 1月, 2012 1 次提交
  22. 03 1月, 2012 1 次提交
  23. 20 12月, 2011 1 次提交
  24. 13 12月, 2011 1 次提交
  25. 28 11月, 2011 1 次提交
  26. 15 11月, 2011 1 次提交
  27. 24 10月, 2011 1 次提交
    • A
      mfd: remove CONFIG_MFD_SUPPORT · 8a0a8e8e
      Arnd Bergmann 提交于
      We currently have two symbols to control compilation the MFD subsystem,
      MFD_SUPPORT and MFD_CORE. The MFD_SUPPORT is actually not required
      at all, it only hides the submenu when not set, with the effect that
      Kconfig warns about missing dependencies when another driver selects
      an MFD driver while MFD_SUPPORT is disabled. Turning the MFD submenu
      back from menuconfig into a plain menu simplifies the Kconfig syntax
      for those kinds of users and avoids the surprise when the menu
      suddenly appears because another driver was enabled that selects this
      symbol.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      8a0a8e8e
  28. 06 10月, 2011 2 次提交
  29. 23 9月, 2011 1 次提交
  30. 21 9月, 2011 4 次提交
  31. 08 9月, 2011 1 次提交
  32. 01 8月, 2011 3 次提交