1. 12 8月, 2015 11 次提交
  2. 05 8月, 2015 3 次提交
    • G
      ARM: shmobile: sh73a0 dtsi: Add missing "gpio-ranges" to gpio node · 94bdc48d
      Geert Uytterhoeven 提交于
      If a GPIO driver uses gpiochip_add_pin_range() (which is usually the
      case for GPIO/PFC combos), the GPIO hogging mechanism configured from DT
      doesn't work:
      
          requesting hog GPIO led1-high (chip sh73a0_pfc, offset 20) failed
      
      The actual error code is -517 == -EPROBE_DEFER.
      
      The problem is that PFC+GPIO registration is handled in multiple steps:
        1. pinctrl_register(),
        2. gpiochip_add(),
        3. gpiochip_add_pin_range().
      
      Configuration of the hogs is handled in gpiochip_add():
      
          gpiochip_add
              of_gpiochip_add
                  of_gpiochip_scan_hogs
                      gpiod_hog
                          gpiochip_request_own_desc
                              __gpiod_request
                                  chip->request
                                      pinctrl_request_gpio
                                          pinctrl_get_device_gpio_range
      
      However, at this point the GPIO controller hasn't been added to
      pinctrldev_list yet, so the range can't be found, and the operation fails
      with -EPROBE_DEFER.
      
      To fix this, add a "gpio-ranges" property to the gpio device node, so
      the ranges are added by of_gpiochip_add_pin_range(), which is called by
      of_gpiochip_add() before the call to of_gpiochip_scan_hogs().
      Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      94bdc48d
    • G
      ARM: shmobile: r8a7740 dtsi: Add missing "gpio-ranges" to gpio node · 09d1c7b4
      Geert Uytterhoeven 提交于
      If a GPIO driver uses gpiochip_add_pin_range() (which is usually the
      case for GPIO/PFC combos), the GPIO hogging mechanism configured from DT
      doesn't work:
      
          requesting hog GPIO lcd0 (chip r8a7740_pfc, offset 176) failed
      
      The actual error code is -517 == -EPROBE_DEFER.
      
      The problem is that PFC+GPIO registration is handled in multiple steps:
        1. pinctrl_register(),
        2. gpiochip_add(),
        3. gpiochip_add_pin_range().
      
      Configuration of the hogs is handled in gpiochip_add():
      
          gpiochip_add
              of_gpiochip_add
                  of_gpiochip_scan_hogs
                      gpiod_hog
                          gpiochip_request_own_desc
                              __gpiod_request
                                  chip->request
                                      pinctrl_request_gpio
                                          pinctrl_get_device_gpio_range
      
      However, at this point the GPIO controller hasn't been added to
      pinctrldev_list yet, so the range can't be found, and the operation fails
      with -EPROBE_DEFER.
      
      To fix this, add a "gpio-ranges" property to the gpio device node, so
      the range is added by of_gpiochip_add_pin_range(), which is called by
      of_gpiochip_add() before the call to of_gpiochip_scan_hogs().
      Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      09d1c7b4
    • G
      ARM: shmobile: r8a73a4 dtsi: Add missing "gpio-ranges" to gpio node · 17ccec50
      Geert Uytterhoeven 提交于
      If a GPIO driver uses gpiochip_add_pin_range() (which is usually the
      case for GPIO/PFC combos), the GPIO hogging mechanism configured from DT
      doesn't work:
      
          requesting hog GPIO led1-high (chip r8a73a4_pfc, offset 28) failed
      
      The actual error code is -517 == -EPROBE_DEFER.
      
      The problem is that PFC+GPIO registration is handled in multiple steps:
        1. pinctrl_register(),
        2. gpiochip_add(),
        3. gpiochip_add_pin_range().
      
      Configuration of the hogs is handled in gpiochip_add():
      
          gpiochip_add
              of_gpiochip_add
                  of_gpiochip_scan_hogs
                      gpiod_hog
                          gpiochip_request_own_desc
                              __gpiod_request
                                  chip->request
                                      pinctrl_request_gpio
                                          pinctrl_get_device_gpio_range
      
      However, at this point the GPIO controller hasn't been added to
      pinctrldev_list yet, so the range can't be found, and the operation fails
      with -EPROBE_DEFER.
      
      To fix this, add a "gpio-ranges" property to the gpio device node, so
      the ranges are added by of_gpiochip_add_pin_range(), which is called by
      of_gpiochip_add() before the call to of_gpiochip_scan_hogs().
      Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Acked-by: NLaurent Pinchart <laurent.pinchart@ideasonboard.com>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NSimon Horman <horms+renesas@verge.net.au>
      17ccec50
  3. 03 8月, 2015 2 次提交
  4. 30 7月, 2015 2 次提交
  5. 29 7月, 2015 1 次提交
  6. 28 7月, 2015 2 次提交
  7. 22 7月, 2015 5 次提交
  8. 15 7月, 2015 4 次提交
  9. 06 7月, 2015 10 次提交