2019-01-02 08:47:02 +08:00
|
|
|
# Kconfig - MIMXRT1020-EVK board
|
|
|
|
#
|
|
|
|
# Copyright (c) 2018, NXP
|
|
|
|
#
|
|
|
|
# SPDX-License-Identifier: Apache-2.0
|
|
|
|
#
|
|
|
|
|
|
|
|
if BOARD_MIMXRT1020_EVK
|
|
|
|
|
|
|
|
config BOARD
|
|
|
|
default "mimxrt1020_evk" if BOARD_MIMXRT1020_EVK
|
|
|
|
|
2019-02-15 23:11:25 +08:00
|
|
|
choice CODE_LOCATION
|
|
|
|
default CODE_FLEXSPI
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
choice DATA_LOCATION
|
|
|
|
default DATA_SEMC
|
|
|
|
endchoice
|
|
|
|
|
2019-01-02 08:47:02 +08:00
|
|
|
if GPIO_MCUX_IGPIO
|
|
|
|
|
|
|
|
config GPIO_MCUX_IGPIO_1
|
|
|
|
default y
|
|
|
|
|
|
|
|
config GPIO_MCUX_IGPIO_5
|
|
|
|
default y
|
|
|
|
|
|
|
|
endif # GPIO_MCUX_IGPIO
|
|
|
|
|
2019-01-20 22:37:42 +08:00
|
|
|
if I2C_MCUX_LPI2C
|
|
|
|
|
|
|
|
config I2C_1
|
|
|
|
default y
|
|
|
|
|
|
|
|
config I2C_4
|
|
|
|
default y
|
|
|
|
|
|
|
|
endif # I2C_MCUX_LPI2C
|
|
|
|
|
2019-01-02 08:47:02 +08:00
|
|
|
if UART_MCUX_LPUART
|
|
|
|
|
|
|
|
config UART_MCUX_LPUART_1
|
|
|
|
default y
|
|
|
|
|
2019-01-15 05:14:37 +08:00
|
|
|
config UART_MCUX_LPUART_2
|
|
|
|
default y if BT_UART
|
|
|
|
|
2019-01-02 08:47:02 +08:00
|
|
|
endif # UART_MCUX_LPUART
|
|
|
|
|
2019-01-21 04:14:08 +08:00
|
|
|
if NETWORKING
|
|
|
|
|
|
|
|
config NET_L2_ETHERNET
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y
|
2019-01-21 04:14:08 +08:00
|
|
|
|
|
|
|
config ETH_MCUX_0
|
kconfig: Use 'default' instead of 'def_bool' in Kconfig.defconfig files
Same deal as in commit 4638652214 ("Kconfig: Use 'default' instead of
'def_bool' in Kconfig.defconfig files"), fixing new stuff that got
introduced since then.
Some symbols, like ALTERA_AVALON_PIO, are only defined in
Kconfig.defconfig files, and so need the def_bool.
Motivation (from the note at the end of
guides/kconfig/index.html#common-shorthands):
For a symbol defined in multiple locations (e.g., in a Kconfig.defconfig
file in Zephyr), it is best to only give the symbol type for the "base"
definition of the symbol, and to use 'default' (instead of 'def_<type>'
value) for the remaining definitions. That way, if the base definition
of the symbol is removed, the symbol ends up without a type, which
generates a warning that points to the other definitions. That makes the
extra definitions easier to discover and remove.
Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-03-18 19:29:31 +08:00
|
|
|
default y if NET_L2_ETHERNET
|
2019-01-21 04:14:08 +08:00
|
|
|
|
|
|
|
endif # NETWORKING
|
|
|
|
|
2019-01-02 08:47:02 +08:00
|
|
|
endif # BOARD_MIMXRT1020_EVK
|