summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2011-10-21 12:25:53 -0600
committerLinus Walleij <linus.walleij@linaro.org>2012-01-03 09:09:59 +0100
commit3712a3c488987849613a4ad74129e67e40b12b38 (patch)
treec3b155ed171bb0542d6ea4b18dcfc3d279ee610f /net
parentd2f6a1c6fb0e510a24ccac066eefbcfd0c932858 (diff)
downloadlinux-3712a3c488987849613a4ad74129e67e40b12b38.tar.gz
linux-3712a3c488987849613a4ad74129e67e40b12b38.tar.bz2
linux-3712a3c488987849613a4ad74129e67e40b12b38.zip
pinctrl: add explicit gpio_disable_free pinmux_op
Some pinctrl drivers (Tegra at least) program a pin to be a GPIO in a completely different manner than they select which function to mux out of that pin. In order to support a single "free" pinmux_op, the driver would need to maintain a per-pin state of requested-for-gpio vs. requested-for- function. However, that's a lot of work when the core already has explicit separate paths for gpio request/free and function request/free. So, add a gpio_disable_free op to struct pinmux_ops, and make pin_free() call it when appropriate. When doing this, I noticed that when calling pin_request(): !!gpio == (gpio_range != NULL) ... and so I collapsed those two parameters in both pin_request(), and when adding writing the new code in pin_free(). Also, for pin_free(): !!free_func == (gpio_range != NULL) However, I didn't want pin_free() to know about the GPIO function naming special case, so instead, I reworked pin_free() to always return the pin's previously requested function, and now pinmux_free_gpio() calls kfree(function). This is much more balanced with the allocation having been performed in pinmux_request_gpio(). Signed-off-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions