diff options
| author | Haojian Zhuang <haojian.zhuang@linaro.org> | 2013-02-17 19:42:50 +0800 |
|---|---|---|
| committer | Linus Walleij <linus.walleij@linaro.org> | 2013-03-07 05:27:30 +0100 |
| commit | 51e13c2475913d45a3ec546dee647538a9341d6a (patch) | |
| tree | 4dc33099bddd1860ac04c6007611329b5789e2b4 /drivers/gpio/gpio-pl061.c | |
| parent | f1f70479e999217ecbf619d71837fc5d77c680fb (diff) | |
| download | lwn-51e13c2475913d45a3ec546dee647538a9341d6a.tar.gz lwn-51e13c2475913d45a3ec546dee647538a9341d6a.zip | |
pinctrl: check pinctrl ready for gpio range
pinctrl_get_device_gpio_range() only checks whether a certain GPIO pin
is in gpio range. But maybe some GPIO pins don't have back-end pinctrl
interface, it means that these pins are always configured as GPIO
function. For example, gpio159 isn't related to back-end pinctrl device
in Hi3620 while other GPIO pins are related to back-end pinctrl device.
Append pinctrl_ready_for_gpio_range() that is used to check whether
pinctrl device with GPIO range is ready. This function will be called
after pinctrl_get_device_gpio_range() fails.
If pinctrl device with GPIO range is found, it means that pinctrl device
is already launched and a certain GPIO pin just don't have back-end pinctrl
interface. Then pinctrl_request_gpio() shouldn't return -EPROBE_DEFER in
this case.
Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/gpio/gpio-pl061.c')
0 files changed, 0 insertions, 0 deletions