kconfig: Adjust ordering so that defaults work as expected
At present defaults in arch-specific Kconfig files are ignored if the top-level item comes ahead of it in include order. This means that it is not possible to have a U-Boot default that architectures and boards can override. This does not seem very useful. Move the include earlier to support this. Signed-off-by: Simon Glass <sjg@chromium.org> Reported-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Reviewed-by: Masahiro Yamada <yamada.m@jp.panasonic.com>utp
parent
6d4d05b1e9
commit
66afaef228
5
Kconfig
5
Kconfig
|
@ -12,6 +12,9 @@ config KCONFIG_OBJDIR
|
||||||
string
|
string
|
||||||
option env="KCONFIG_OBJDIR"
|
option env="KCONFIG_OBJDIR"
|
||||||
|
|
||||||
|
# Allow defaults in arch-specific code to override any given here
|
||||||
|
source "arch/Kconfig"
|
||||||
|
|
||||||
menu "General setup"
|
menu "General setup"
|
||||||
|
|
||||||
config LOCALVERSION
|
config LOCALVERSION
|
||||||
|
@ -172,8 +175,6 @@ config SYS_CLK_FREQ
|
||||||
|
|
||||||
endmenu # Boot images
|
endmenu # Boot images
|
||||||
|
|
||||||
source "arch/Kconfig"
|
|
||||||
|
|
||||||
source "common/Kconfig"
|
source "common/Kconfig"
|
||||||
|
|
||||||
source "dts/Kconfig"
|
source "dts/Kconfig"
|
||||||
|
|
Loading…
Reference in New Issue