While migrating individual status led usages to Kconfig stuff,
a (random) value was introduced for this board which does not
work but produces the following error message during boot:
__led_init: failed requesting GPIO59!
Since Kconfig does not seem to accept a define as this point,
but the mxs gpio driver requires not only a simple integer value,
we need to use the plain value of MX23_PAD_SSP1_DETECT__GPIO_2_1.
Signed-off-by: Michael Heimpold <mhei@heimpold.de>
Fixes: 2d8d190c83
("status_led: Kconfig migration")
43 lines
982 B
Plaintext
43 lines
982 B
Plaintext
CONFIG_ARM=y
|
|
CONFIG_ARCH_MX23=y
|
|
CONFIG_SYS_TEXT_BASE=0x40002000
|
|
CONFIG_SPL_GPIO_SUPPORT=y
|
|
CONFIG_SPL_LIBCOMMON_SUPPORT=y
|
|
CONFIG_SPL_LIBGENERIC_SUPPORT=y
|
|
CONFIG_TARGET_MX23_OLINUXINO=y
|
|
CONFIG_SPL_SERIAL_SUPPORT=y
|
|
CONFIG_SPL=y
|
|
CONFIG_NR_DRAM_BANKS=1
|
|
CONFIG_BOOTDELAY=3
|
|
CONFIG_VERSION_VARIABLE=y
|
|
# CONFIG_DISPLAY_BOARDINFO is not set
|
|
CONFIG_ARCH_MISC_INIT=y
|
|
# CONFIG_SPL_FRAMEWORK is not set
|
|
CONFIG_HUSH_PARSER=y
|
|
# CONFIG_CMD_FLASH is not set
|
|
CONFIG_CMD_GPIO=y
|
|
CONFIG_CMD_MMC=y
|
|
CONFIG_CMD_USB=y
|
|
# CONFIG_CMD_SETEXPR is not set
|
|
CONFIG_CMD_DHCP=y
|
|
CONFIG_CMD_CACHE=y
|
|
CONFIG_CMD_EXT2=y
|
|
CONFIG_CMD_FAT=y
|
|
CONFIG_ENV_IS_IN_MMC=y
|
|
CONFIG_LED_STATUS=y
|
|
CONFIG_LED_STATUS_GPIO=y
|
|
CONFIG_LED_STATUS0=y
|
|
CONFIG_LED_STATUS_BIT=778
|
|
CONFIG_LED_STATUS_STATE=2
|
|
CONFIG_LED_STATUS_BOOT_ENABLE=y
|
|
CONFIG_LED_STATUS_BOOT=0
|
|
CONFIG_LED_STATUS_CMD=y
|
|
CONFIG_MMC_MXS=y
|
|
CONFIG_CONS_INDEX=0
|
|
CONFIG_USB=y
|
|
CONFIG_USB_EHCI_HCD=y
|
|
CONFIG_USB_STORAGE=y
|
|
CONFIG_USB_HOST_ETHER=y
|
|
CONFIG_USB_ETHER_SMSC95XX=y
|
|
CONFIG_OF_LIBFDT=y
|