summaryrefslogtreecommitdiffstats
path: root/drivers/pinctrl/pinctrl-exynos5440.c
diff options
context:
space:
mode:
authorHaojian Zhuang <haojian.zhuang@linaro.org>2013-01-18 15:31:05 +0800
committerLinus Walleij <linus.walleij@linaro.org>2013-01-22 13:48:07 +0100
commit8b77b3762c37c9c2ce72f0d075890a3e8849702f (patch)
tree0ee4142b12c4b353f4be26f5e566972494318f2e /drivers/pinctrl/pinctrl-exynos5440.c
parent889c5d3e76dd506b8d1c3794824132e354b8255c (diff)
downloadtalos-op-linux-8b77b3762c37c9c2ce72f0d075890a3e8849702f.tar.gz
talos-op-linux-8b77b3762c37c9c2ce72f0d075890a3e8849702f.zip
Revert "pinctrl: single: support gpio request and free"
This reverts commit 2e8b2eab94c35d83bb7da71c63b4695f32ddca88. Conflicts: drivers/pinctrl/pinctrl-single.c ERROR: "__aeabi_uldivmod" [drivers/pinctrl/pinctrl-single.ko] undefined!] On Fri, Jan 11, 2013 at 4:00 PM, Russell King wrote: > The above error happens in builds including pinctrl-single - the > reason > is this, where resource_size_t may be 64-bit. > > gpio->range.pin_base = (r.start - pcs->res->start) / > mux_bytes; > gpio->range.npins = (r.end - r.start) / mux_bytes + 1; The reason of not fixing this issue and reverting the patch instead is this patch can't handle another case. It's not easy to handle multiple gpios sharing one pin register. So this gpio range feature will be implemented by other patches. Acked-by: Tony Lindgren <tony@atomide.com> Signed-off-by: Haojian Zhuang <haojian.zhuang@linaro.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'drivers/pinctrl/pinctrl-exynos5440.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud