1. 08 6月, 2016 1 次提交
  2. 07 6月, 2016 1 次提交
  3. 03 5月, 2016 4 次提交
  4. 29 4月, 2016 1 次提交
    • A
      gpio/qoriq: select IRQ_DOMAIN · a8fa91a7
      Arnd Bergmann 提交于
      The gpio-mpc8xxx driver requires IRQ domains but can be built
      without them, resulting on a failure to build certain randconfigs
      on ARM:
      
      drivers/gpio/gpio-mpc8xxx.c: In function 'mpc8xxx_gpio_to_irq':
      drivers/gpio/gpio-mpc8xxx.c:92:10: error: implicit declaration of function 'irq_create_mapping' [-Werror=implicit-function-declaration]
         return irq_create_mapping(mpc8xxx_gc->irq, offset);
      
      This selects IRQ_DOMAIN from the driver to ensure we can build it.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Fixes: 5df7fd46 ("gpio/qoriq: Add qoriq platforms support")
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      a8fa91a7
  5. 26 4月, 2016 1 次提交
    • L
      gpio: remove deps on ARCH_[WANT_OPTIONAL|REQUIRE]_GPIOLIB · 296ad4ac
      Linus Walleij 提交于
      The GPIOLIB symbol currently require that
      ARCH_WANT_OPTIONAL_GPIOLIB or ARCH_REQUIRE_GPIOLIB is selected
      to be selectable.
      
      The ARCH_REQUIRE_GPIOLIB does only one thing: select GPIOLIB.
      
      This is just confusing: architectures that want GPIOLIB should
      be able to configure it in no matter what, and those who
      require it should just select GPIOLIB.
      
      It also creates problems for drivers that need to state
      "select GPIOLIB" to get dependencies: those depend on the
      selected architecture to select
      ARCH_[WANT_OPTIONAL|REQUIRE]_GPIOLIB first, and will cause
      compile errors for the few archs that state neither.
      
      These intermediary symbols need to go.
      
      As a first step, remove the dependencies so that:
      
      - ARCH_WANT_OPTIONAL_GPIOLIB becomes a noop (GPIOLIB will be
        available for everyone) and
      
      - "select ARCH_REQUIRE_GPIOLIB" can be replaced by just
        "select GPIOLIB"
      
      After this patch we can follow up with patches cleaning up the
      architectures one-by one and eventually remove the
      ARCH_[WANT_OPTIONAL|REQUIRE]_GPIOLIB symbols altogether.
      Reported-by: NMichael Hennerich <michael.hennerich@analog.com>
      Cc: Michael Büsch <m@bues.ch>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      296ad4ac
  6. 14 4月, 2016 2 次提交
  7. 10 4月, 2016 1 次提交
  8. 31 3月, 2016 2 次提交
  9. 30 3月, 2016 2 次提交
  10. 16 3月, 2016 2 次提交
  11. 09 3月, 2016 1 次提交
  12. 08 3月, 2016 1 次提交
  13. 07 3月, 2016 1 次提交
  14. 25 2月, 2016 3 次提交
  15. 12 2月, 2016 2 次提交
  16. 11 2月, 2016 1 次提交
    • N
      gpio: add tps65218 gpio · c366c76a
      Nicolas Saenz Julienne 提交于
      Driver for the GPIO block found in ti's tps65218 pmics.
      
      The device has two GPIOs and one GPO pin which can be configured as follows:
      GPIO1:
      	-general-purpose, open-drain output controlled by GPO1 user bit and/or
      	 sequencer
      	-DDR3 reset input signal from SOC. Signal is either latched or
      	 passed-trough to GPO2 pin. See below for details.
      GPO2:
      	-general-purpose output controlled by GPO2 user bit
      	-DDR3 reset output signal. Signal is controlled by GPIO1 and PGOOD.
      	 See below for details.
      	-Output buffer can be configured as open-drain or push-pull.
      GPIO3:
      	-general-purpose, open-drain output controlled by GPO3 user bit and/or
      	 sequencer
      	-reset input-signal for DCDC1 and DCDC2.
      
      The input configurations are not meant to be used by the user so the driver
      only offers GPOs.
      
      v2: Added request routine that evaluates the fw config flags and removed module
          owner
      v3: Added .direction_input() routine, and took care of all Linus Walleij
      suggestions (clamp to bool, use proper include)
      Signed-off-by: NNicolas Saenz Julienne <nicolassaenzj@gmail.com>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      c366c76a
  17. 10 2月, 2016 5 次提交
  18. 05 2月, 2016 1 次提交
  19. 28 1月, 2016 4 次提交
  20. 07 1月, 2016 1 次提交
  21. 11 12月, 2015 2 次提交
  22. 02 12月, 2015 1 次提交
    • A
      gpio: samsung: move gpio-samsung driver back to platform code · 0f20e456
      Arnd Bergmann 提交于
      The gpio-samsung driver is special in the sense that it
      interacts directly in multiple ways with the legacy platform
      code for the s3c24xx and s3c64xx platforms. In contrast,
      all devicetree based machines for Samsung, including the
      ones on those two SoC families use a different driver.
      
      The header files that define the interface between the platform
      code and the gpio driver are not visible when building a
      kernel for ARCH_MULTIPLATFORM, which prevents us from
      turning on this option for s3c64xx.
      
      To work around this, we now move the driver back into platform
      code, from where it was originally moved to as part of commit
      1b39d5f2 ("gpio/samsung: gpio-samsung.c to support
      Samsung GPIOs").
      
      The long-term plan for this driver would be to remove it
      entirely, after all Samsung machines have been converted
      over to boot from DT, but there is currently no timeline
      for when that might happen.
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Reviewed-by: NKrzysztof Kozlowski <k.kozlowski@samsung.com>
      0f20e456