summaryrefslogtreecommitdiffstats
path: root/arch/arm/mach-omap2
diff options
context:
space:
mode:
authorArnd Bergmann <arnd@arndb.de>2012-08-15 20:34:48 +0000
committerArnd Bergmann <arnd@arndb.de>2012-08-23 17:27:45 +0200
commitdb43b184685632b7c23ccd47ec08b61010d55798 (patch)
treeb6587067bf12ee2a0c48052d777819c4ba7daaa0 /arch/arm/mach-omap2
parent1fc593feaf8e440511f381f4cdff483b55bbf546 (diff)
downloadblackbird-op-linux-db43b184685632b7c23ccd47ec08b61010d55798.tar.gz
blackbird-op-linux-db43b184685632b7c23ccd47ec08b61010d55798.zip
ARM: ux500: don't select LEDS_GPIO for snowball
Using 'select' in Kconfig is hard, a platform cannot just enable a driver without also making sure that its subsystem is there. Also, there is no actual code dependency between the platform and the gpio leds driver. Without this patch, building without LEDS_CLASS esults in: drivers/built-in.o: In function `create_gpio_led.part.2': governor_userspace.c:(.devinit.text+0x5a58): undefined reference to `led_classdev_register' drivers/built-in.o: In function `gpio_led_remove': governor_userspace.c:(.devexit.text+0x6b8): undefined reference to `led_classdev_unregister' This reverts 8733f53c6 "ARM: ux500: Kconfig: Compile in leds-gpio support for Snowball" that introduced the regression and did not provide a helpful explanation. In order to leave the GPIO LED code still present in normal builds, this also enables the symbol in u8500_defconfig, in addition to the other LED drivers that are already selected there. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Cc: Linus Walleij <linus.walleij@linaro.org> Cc: Lee Jones <lee.jones@linaro.org>
Diffstat (limited to 'arch/arm/mach-omap2')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud