1. 20 5月, 2012 1 次提交
    • S
      gpio/generic: initialize basic_mmio_gpio shadow variables properly · 3e11f7b8
      Shawn Guo 提交于
      It fixes the issue in gpio-generic that commit fb149218 (gpio/mxc: add
      missing initialization of basic_mmio_gpio shadow variables) manged to
      fix in gpio-mxc driver, so that other platform specific drivers do not
      suffer from the same problem over and over again.
      
      Changes since v1:
      * Turn the last parameter of bgpio_init() "bool big_endian" into
        "unsigned long flags" and give those really quirky hardwares a
        chance to tell that reg_set and reg_dir are unreadable.
      Signed-off-by: NShawn Guo <shawn.guo@linaro.org>
      [grant.likely: Fix big-endian usage to explicitly set BBGPIOF_BIG_ENDIAN]
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      3e11f7b8
  2. 01 11月, 2011 1 次提交
  3. 22 9月, 2011 1 次提交
  4. 17 8月, 2011 1 次提交
  5. 16 8月, 2011 1 次提交
  6. 20 7月, 2011 1 次提交
  7. 09 7月, 2011 2 次提交
  8. 08 7月, 2011 1 次提交
    • L
      gpio/mxc: add missing initialization of basic_mmio_gpio shadow variables · fb149218
      Lothar Waßmann 提交于
      The bgpio_init() function does not initialise the shadow register for
      the GPIO direction register. Thus, when configuring the first GPIO with
      gpio_set_direction() all other GPIOs of the same bank will be
      configured as inputs. Since the bgpio layer cannot know whether the
      register is readable, the initialisation should be done by the caller
      of bgpio_init().
      
      Also, the 'data' shadow variable that is used inside basic_mmio_gpio
      to cache the current value of the GPIO_DR register is initialised from
      the GPIO_PSR register within bgpio_init(). Thus when setting the
      output value of a certain GPIO, the other GPIO outputs of the same
      bank will be set or cleared depending on the pin state of the GPIO
      inputs during bgpio_init().
      Signed-off-by: NLothar Waßmann <LW@KARO-electronics.de>
      Signed-off-by: NGrant Likely <grant.likely@secretlab.ca>
      fb149218
  9. 12 6月, 2011 1 次提交
  10. 07 6月, 2011 4 次提交
  11. 12 4月, 2011 1 次提交
  12. 29 3月, 2011 2 次提交
  13. 08 3月, 2011 1 次提交
  14. 01 2月, 2011 1 次提交
  15. 14 1月, 2011 1 次提交
  16. 03 1月, 2011 2 次提交
  17. 20 11月, 2010 3 次提交
  18. 17 11月, 2010 3 次提交
  19. 26 10月, 2010 1 次提交
  20. 11 10月, 2010 1 次提交
  21. 28 7月, 2010 1 次提交
  22. 26 7月, 2010 1 次提交
  23. 22 4月, 2010 1 次提交
  24. 24 2月, 2010 4 次提交
  25. 14 11月, 2009 1 次提交
    • U
      imx/gpio: Use handle_level_irq · 060d20d3
      Uwe Kleine-König 提交于
      According to Russell King handle_edge_irq is only useful for "edge-based
      inputs where the controller does not remember transitions with the input
      masked."
      
      So using handle_edge_irq unconditionally for both edge and level irqs is
      wrong.  Testing showed that the controller does remember transitions
      while the interrupt is masked.  So use handle_level_irq unconditionally.
      Signed-off-by: NUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Cc: Russell King <rmk@arm.linux.org.uk>
      Cc: Sascha Hauer <s.hauer@pengutronix.de>
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      060d20d3
  26. 14 8月, 2009 1 次提交
  27. 07 8月, 2009 1 次提交