diff options
author | Gregory CLEMENT <gregory.clement@free-electrons.com> | 2013-05-17 14:25:03 +0200 |
---|---|---|
committer | Jason Cooper <jason@lakedaemon.net> | 2013-05-19 19:38:59 +0000 |
commit | c689cbac25b4fce2f3d7de2e4dd6678caeebdcb8 (patch) | |
tree | 751b99621a2f2a890cacd80408f70a8cd847c95b /arch/arm/boot/dts/armada-370.dtsi | |
parent | c6c003af0b91bb8722dbf2a8683cd40532e12079 (diff) | |
download | linux-c689cbac25b4fce2f3d7de2e4dd6678caeebdcb8.tar.bz2 |
ARM: mvebu: select ARCH_REQUIRE_GPIOLIB for mvebu platform
Initially ARCH_REQUIRE_GPIOLIB was part of Thomas Petazzoni series
when he introduced the gpiolib support for mvebu:
93a59cf arm: mvebu: use GPIO support now that a driver is available
This commit was written to be applied for the ARCH_MVEBU which was
located in arch/arm/KConfig and was merged in 3.7.
In the same time Rob Herring moved the ARCH_MVEBU block to
arch/arm/mach-mvebu/Kconfig with this commit and also merged in 3.7:
387798b ARM: initial multiplatform support
Unfortunately the ARCH_REQUIRE_GPIOLIB have been lost during this
migration. This was not noticed until the v3.10-rc1, because mvebu as
part of ARCH_MULTIPLATFORM was always selected with ARCH_VEXPRESS, and
this architect selected ARCH_REQUIRE_GPIOLIB.
Since the following commit from Arnd: "883a106 ARM: default machine
descriptor for multiplatform", ARCH_VEXPRESS was then no more selected
by default with ARCH_MVEBU and it made appeared the lack of
ARCH_REQUIRE_GPIOLIB for mvebu. This commit added back the selection
of ARCH_REQUIRE_GPIOLIB for ARCH_MVEBU.
Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
Signed-off-by: Jason Cooper <jason@lakedaemon.net>
Diffstat (limited to 'arch/arm/boot/dts/armada-370.dtsi')
0 files changed, 0 insertions, 0 deletions