1. 17 1月, 2013 2 次提交
  2. 10 1月, 2013 1 次提交
  3. 20 12月, 2012 2 次提交
  4. 10 12月, 2012 2 次提交
  5. 07 12月, 2012 1 次提交
  6. 03 12月, 2012 1 次提交
  7. 02 12月, 2012 1 次提交
  8. 01 12月, 2012 1 次提交
  9. 30 11月, 2012 2 次提交
  10. 29 11月, 2012 5 次提交
  11. 24 11月, 2012 1 次提交
  12. 21 11月, 2012 6 次提交
  13. 20 11月, 2012 2 次提交
  14. 18 11月, 2012 9 次提交
  15. 15 11月, 2012 1 次提交
  16. 14 11月, 2012 1 次提交
  17. 12 11月, 2012 2 次提交
    • L
      gpiolib: separation of pin concerns · 1e63d7b9
      Linus Walleij 提交于
      The fact that of_gpiochip_add_pin_range() and
      gpiochip_add_pin_range() share too much code is fragile and
      will invariably mean that bugs need to be fixed in two places
      instead of one.
      
      So separate the concerns of gpiolib.c and gpiolib-of.c and
      have the latter call the former as back-end. This is necessary
      also when going forward with other device descriptions such
      as ACPI.
      
      This is done by:
      
      - Adding a return code to gpiochip_add_pin_range() so we can
        reliably check whether this succeeds.
      
      - Get rid of the custom of_pinctrl_add_gpio_range() from
        pinctrl. Instead create of_pinctrl_get() to just retrive the
        pin controller per se from an OF node. This composite
        function was just begging to be deleted, it was way to
        purpose-specific.
      
      - Use pinctrl_dev_get_name() to get the name of the retrieved
        pin controller and use that to call back into the generic
        gpiochip_add_pin_range().
      
      Now the pin range is only allocated and tied to a pin
      controller from the core implementation in gpiolib.c.
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      1e63d7b9
    • L
      gpiolib: call pin removal in chip removal function · 9ef0d6f7
      Linus Walleij 提交于
      This makes us call gpiochio_remove_pin_ranges() in the
      gpiochip_remove() function, so we get rid of ranges when
      freeing the chip.
      Reviewed-by: NStephen Warren <swarren@nvidia.com>
      Reviewed-by: NViresh Kumar <viresh.kumar@linaro.org>
      Signed-off-by: NLinus Walleij <linus.walleij@linaro.org>
      9ef0d6f7