ARM: shmobile: armadillo800eva: Don't request GPIO 166 in board code
authorKuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Thu, 25 Jul 2013 00:50:50 +0000 (17:50 -0700)
committerSimon Horman <horms+renesas@verge.net.au>
Thu, 25 Jul 2013 05:40:31 +0000 (14:40 +0900)
commit16b551dd22cc7edacb952f7a2e175f36c3aa4bdb
tree59213e2a37272f835e971d5c8eec5fe2d5458b63
parentad81f0545ef01ea651886dddac4bef6cec930092
ARM: shmobile: armadillo800eva: Don't request GPIO 166 in board code

89ae7b5bbd3e65bc6ab7a577ca5ec18569589c8c
(ARM: shmobile: armadillo800eva: Register pinctrl mapping for INTC)
mistakenly requests GPIO 166 in board code,
most probably due to a wrong merge conflict resolution.
As the GPIO is passed to the st1232 driver through platform
data and requested by the driver,
there's no need to request it in board code. Fix it.

Tested by: Cao Minh Hiep <cm-hiep@jinso.co.jp>
Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
arch/arm/mach-shmobile/board-armadillo800eva.c