mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-12-11 22:03:15 +00:00
58d423b88e
As mentioned in the previous commit, adding default values in each Kconfig causes problems because it does not co-exist with the "depends on" syntax. (Please note this is not a bug of Kconfig.) We should not do so unless we have a special reason. Actually, for CONFIG_DM*, we have no good reason to do so. Generally, CONFIG_DM is not a user-configurable option. Once we convert a driver into Driver Model, the board only works with Driver Model, i.e. CONFIG_DM must be always enabled for that board. So, using "select DM" is more suitable rather than allowing users to modify it. Another good thing is, Kconfig warns unmet dependencies for "select" syntax, so we easily notice bugs. Actually, CONFIG_DM and other related options have been added without consistency: some into arch/*/Kconfig, some into board/*/Kconfig, and some into configs/*_defconfig. This commit prefers "select" and cleans up the following issues. [1] Never use "CONFIG_DM=n" in defconfig files It is really rare to add "CONFIG_FOO=n" to disable CONFIG options. It is more common to use "# CONFIG_FOO is not set". But here, we do not even have to do it. Less than half of OMAP3 boards have been converted to Driver Model. Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is weird. Instead, add "select DM" only to appropriate boards, which eventually eliminates "CONFIG_DM=n", etc. [2] Delete redundant CONFIGs Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again in configs/sandbox_defconfig. Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and defines it also in omap3_beagle_defconfig and devkit8000_defconfig. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
41 lines
1 KiB
Text
41 lines
1 KiB
Text
if TARGET_AM335X_EVM
|
|
|
|
config SYS_BOARD
|
|
default "am335x"
|
|
|
|
config SYS_VENDOR
|
|
default "ti"
|
|
|
|
config SYS_SOC
|
|
default "am33xx"
|
|
|
|
config SYS_CONFIG_NAME
|
|
default "am335x_evm"
|
|
|
|
config CONS_INDEX
|
|
int "UART used for console"
|
|
range 1 6
|
|
default 1
|
|
help
|
|
The AM335x SoC has a total of 6 UARTs (UART0 to UART5 as referenced
|
|
in documentation, etc) available to it. Depending on your specific
|
|
board you may want something other than UART0 as for example the IDK
|
|
uses UART3 so enter 4 here.
|
|
|
|
config NOR
|
|
bool "Support for NOR flash"
|
|
help
|
|
The AM335x SoC supports having a NOR flash connected to the GPMC.
|
|
In practice this is seen as a NOR flash module connected to the
|
|
"memory cape" for the BeagleBone family.
|
|
|
|
config NOR_BOOT
|
|
bool "Support for booting from NOR flash"
|
|
depends on NOR
|
|
help
|
|
Enabling this will make a U-Boot binary that is capable of being
|
|
booted via NOR. In this case we will enable certain pinmux early
|
|
as the ROM only partially sets up pinmux. We also default to using
|
|
NOR for environment.
|
|
|
|
endif
|