1. 09 1月, 2018 1 次提交
  2. 07 12月, 2017 1 次提交
  3. 08 11月, 2017 1 次提交
  4. 31 10月, 2017 2 次提交
  5. 23 10月, 2017 1 次提交
    • M
      gpio: uniphier: add UniPhier GPIO controller driver · dbe776c2
      Masahiro Yamada 提交于
      This GPIO controller is used on UniPhier SoC family.
      
      It also serves as an interrupt controller, but interrupt signals are
      just delivered to the parent irqchip without any latching or OR'ing.
      This type of hardware can be well described with hierarchy IRQ domain.
      
      One unfortunate thing for this device is that the interrupt mapping to
      the interrupt parent is not contiguous.
      
      I asked how DT can describe interrupt mapping between two irqchips [1],
      but I could not find a good solution (at least in the framework level).
      In fact, irqchip drivers using hierarchy domain generally hard-code the
      DT binding of their parent.
      
      After tackling on several approaches such as hard-code of hwirqs,
      irq_domain_push_irq(), I ended up with a vendor specific property.
      If we come up with a good idea to support this in the framework, we
      can migrate over to it, but we can live with a driver-level solution
      for now.
      
      [1] https://lkml.org/lkml/2017/7/6/758Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      dbe776c2
  6. 20 10月, 2017 1 次提交
    • L
      gpio: Add driver for Maxim MAX3191x industrial serializer · b2f68edf
      Lukas Wunner 提交于
      The driver was developed for and tested with the MAX31913 built into
      the Revolution Pi by KUNBUS, but should work with all members of the
      MAX3191x family:
      
      MAX31910: low power
      MAX31911: LED drivers
      MAX31912: LED drivers + 2nd voltage monitor + low power
      MAX31913: LED drivers + 2nd voltage monitor
      MAX31953: LED drivers + 2nd voltage monitor + isolation
      MAX31963: LED drivers + 2nd voltage monitor + isolation + buck regulator
      
      Cc: Mathias Duckeck <m.duckeck@kunbus.de>
      Signed-off-by: NLukas Wunner <lukas@wunner.de>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      b2f68edf
  7. 17 10月, 2017 1 次提交
  8. 19 9月, 2017 1 次提交
  9. 22 8月, 2017 1 次提交
  10. 21 8月, 2017 1 次提交
  11. 14 8月, 2017 1 次提交
  12. 01 8月, 2017 1 次提交
  13. 21 6月, 2017 1 次提交
  14. 31 5月, 2017 1 次提交
  15. 29 5月, 2017 2 次提交
  16. 24 5月, 2017 1 次提交
  17. 23 5月, 2017 2 次提交
  18. 22 5月, 2017 2 次提交
  19. 28 4月, 2017 1 次提交
  20. 27 4月, 2017 1 次提交
  21. 25 4月, 2017 1 次提交
  22. 24 3月, 2017 1 次提交
    • R
      gpio: add generic single-register fixed-direction GPIO driver · 380639c7
      Russell King 提交于
      Add a simple, generic, single register fixed-direction GPIO driver.
      This is able to support a single register with a mixture of inputs
      and outputs.
      
      This is different from gpio-mmio and gpio-74xx-mmio:
      * gpio-mmio doesn't allow a fixed direction, it assumes there is always
        a direction register.
      * gpio-74xx-mmio only supports all-in or all-out setups
      * gpio-74xx-mmio is DT only, this needs to support legacy too
      * they don't double-read when getting the GPIO value, as required by
        some implementations that this driver supports
      * we need to always do 32-bit reads, which bgpio doesn't guarantee
      * the current output state may not be readable from the hardware
        register - reading may reflect input status but not output status.
      Signed-off-by: NRussell King <rmk+kernel@armlinux.org.uk>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      380639c7
  23. 22 3月, 2017 2 次提交
  24. 17 3月, 2017 1 次提交
  25. 15 3月, 2017 1 次提交
  26. 13 2月, 2017 1 次提交
  27. 06 2月, 2017 1 次提交
  28. 05 2月, 2017 1 次提交
  29. 26 1月, 2017 2 次提交
  30. 24 11月, 2016 1 次提交
  31. 22 11月, 2016 2 次提交
  32. 17 11月, 2016 1 次提交
    • K
      gpio: Remove GPIO_DEVRES option · f9c22ec6
      Keno Fischer 提交于
      This option was added in 6a89a314 to
      allow use of the devm_gpio_* functions without CONFIG_GPIOLIB.
      
      However, only a few months later in
      b69ac524, CONFIG_GPIOLIB was added
      as a dependency, defeating the original purpose of this option.
      Instead of that patch, the original commit could have just been
      reverted (and in fact was partially so in
      403c1d0b). Further, since this
      option has a dependency on HAS_IOMEM, even though it does not
      require it, it causes build failures when !HAS_IOMEM (e.g. in a
      uml build).
      
      Fix that by completely removing the option, in essence completing
      the reversion of the original commit.
      Signed-off-by: NKeno Fischer <keno@juliacomputing.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      f9c22ec6
  33. 24 10月, 2016 1 次提交