kbuild: create symbolic link only for ARM, AVR32, SPARC, PowerPC, x86
The symbolic link to SoC/CPU specific header directory is created
during the build, while it is only necessary for ARM, AVR32, SPARC,
x86, and some CPUs of PowerPC. For the other architectures, it just
results in a broken symbolic link.
Introduce CONFIG_CREATE_ARCH_SYMLINK to not create unneeded symbolic
links.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
9 years ago
|
|
|
config CREATE_ARCH_SYMLINK
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config HAVE_ARCH_IOREMAP
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "Architecture select"
|
|
|
|
|
default SANDBOX
|
|
|
|
|
|
|
|
|
|
config ARC
|
|
|
|
|
bool "ARC architecture"
|
|
|
|
|
select ARCH_EARLY_INIT_R
|
|
|
|
|
select ARC_TIMER
|
|
|
|
|
select CLK
|
|
|
|
|
select HAVE_PRIVATE_LIBGCC
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
select TIMER
|
|
|
|
|
|
|
|
|
|
config ARM
|
|
|
|
|
bool "ARM architecture"
|
kbuild: create symbolic link only for ARM, AVR32, SPARC, PowerPC, x86
The symbolic link to SoC/CPU specific header directory is created
during the build, while it is only necessary for ARM, AVR32, SPARC,
x86, and some CPUs of PowerPC. For the other architectures, it just
results in a broken symbolic link.
Introduce CONFIG_CREATE_ARCH_SYMLINK to not create unneeded symbolic
links.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
9 years ago
|
|
|
select CREATE_ARCH_SYMLINK
|
|
|
|
|
select HAVE_PRIVATE_LIBGCC if !ARM64
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
|
|
|
|
|
config M68K
|
|
|
|
|
bool "M68000 architecture"
|
|
|
|
|
select HAVE_PRIVATE_LIBGCC
|
|
|
|
|
select SYS_BOOT_GET_CMDLINE
|
|
|
|
|
select SYS_BOOT_GET_KBD
|
|
|
|
|
|
|
|
|
|
config MICROBLAZE
|
|
|
|
|
bool "MicroBlaze architecture"
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
imply CMD_IRQ
|
|
|
|
|
|
|
|
|
|
config MIPS
|
|
|
|
|
bool "MIPS architecture"
|
|
|
|
|
select HAVE_ARCH_IOREMAP
|
|
|
|
|
select HAVE_PRIVATE_LIBGCC
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
|
|
|
|
|
config NDS32
|
|
|
|
|
bool "NDS32 architecture"
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
|
|
|
|
|
config NIOS2
|
|
|
|
|
bool "Nios II architecture"
|
|
|
|
|
select CPU
|
|
|
|
|
select DM
|
|
|
|
|
select OF_CONTROL
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
imply CMD_DM
|
|
|
|
|
|
|
|
|
|
config PPC
|
|
|
|
|
bool "PowerPC architecture"
|
|
|
|
|
select HAVE_PRIVATE_LIBGCC
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
select SYS_BOOT_GET_CMDLINE
|
|
|
|
|
select SYS_BOOT_GET_KBD
|
|
|
|
|
|
|
|
|
|
config RISCV
|
|
|
|
|
bool "RISC-V architecture"
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
select OF_CONTROL
|
|
|
|
|
select DM
|
|
|
|
|
imply DM_SERIAL
|
|
|
|
|
imply DM_ETH
|
|
|
|
|
imply DM_MMC
|
|
|
|
|
imply DM_SPI
|
|
|
|
|
imply DM_SPI_FLASH
|
|
|
|
|
imply BLK
|
|
|
|
|
imply CLK
|
|
|
|
|
imply MTD
|
|
|
|
|
imply TIMER
|
|
|
|
|
imply CMD_DM
|
|
|
|
|
|
|
|
|
|
config SANDBOX
|
|
|
|
|
bool "Sandbox"
|
|
|
|
|
select BOARD_LATE_INIT
|
dm: select CONFIG_DM* options
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>
10 years ago
|
|
|
select DM
|
|
|
|
|
select DM_GPIO
|
|
|
|
|
select DM_I2C
|
|
|
|
|
select DM_KEYBOARD
|
|
|
|
|
select DM_MMC
|
dm: select CONFIG_DM* options
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>
10 years ago
|
|
|
select DM_SERIAL
|
|
|
|
|
select DM_SPI
|
|
|
|
|
select DM_SPI_FLASH
|
|
|
|
|
select HAVE_BLOCK_DEVICE
|
|
|
|
|
select LZO
|
|
|
|
|
select SPI
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
imply BITREVERSE
|
|
|
|
|
imply CMD_DM
|
|
|
|
|
imply CMD_GETTIME
|
|
|
|
|
imply CMD_HASH
|
|
|
|
|
imply CMD_IO
|
|
|
|
|
imply CMD_IOTRACE
|
|
|
|
|
imply CMD_LZMADEC
|
|
|
|
|
imply CMD_SATA
|
|
|
|
|
imply CMD_SF_TEST
|
|
|
|
|
imply CRC32_VERIFY
|
|
|
|
|
imply FAT_WRITE
|
|
|
|
|
imply FIRMWARE
|
|
|
|
|
imply HASH_VERIFY
|
|
|
|
|
imply LZMA
|
|
|
|
|
imply SCSI
|
|
|
|
|
imply TEE
|
|
|
|
|
imply AVB_VERIFY
|
|
|
|
|
imply LIBAVB
|
|
|
|
|
imply CMD_AVB
|
|
|
|
|
imply UDP_FUNCTION_FASTBOOT
|
|
|
|
|
|
|
|
|
|
config SH
|
|
|
|
|
bool "SuperH architecture"
|
|
|
|
|
select HAVE_PRIVATE_LIBGCC
|
|
|
|
|
|
|
|
|
|
config X86
|
|
|
|
|
bool "x86 architecture"
|
kbuild: create symbolic link only for ARM, AVR32, SPARC, PowerPC, x86
The symbolic link to SoC/CPU specific header directory is created
during the build, while it is only necessary for ARM, AVR32, SPARC,
x86, and some CPUs of PowerPC. For the other architectures, it just
results in a broken symbolic link.
Introduce CONFIG_CREATE_ARCH_SYMLINK to not create unneeded symbolic
links.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: Simon Glass <sjg@chromium.org>
9 years ago
|
|
|
select CREATE_ARCH_SYMLINK
|
dm: select CONFIG_DM* options
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>
10 years ago
|
|
|
select DM
|
|
|
|
|
select DM_PCI
|
|
|
|
|
select HAVE_PRIVATE_LIBGCC
|
|
|
|
|
select OF_CONTROL
|
|
|
|
|
select PCI
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
select TIMER
|
|
|
|
|
select USE_PRIVATE_LIBGCC
|
|
|
|
|
select X86_TSC_TIMER
|
|
|
|
|
imply BLK
|
|
|
|
|
imply CMD_DM
|
|
|
|
|
imply CMD_FPGA_LOADMK
|
|
|
|
|
imply CMD_GETTIME
|
|
|
|
|
imply CMD_IO
|
|
|
|
|
imply CMD_IRQ
|
|
|
|
|
imply CMD_PCI
|
|
|
|
|
imply CMD_SF_TEST
|
|
|
|
|
imply CMD_ZBOOT
|
|
|
|
|
imply DM_ETH
|
|
|
|
|
imply DM_GPIO
|
|
|
|
|
imply DM_KEYBOARD
|
|
|
|
|
imply DM_MMC
|
|
|
|
|
imply DM_RTC
|
|
|
|
|
imply DM_SCSI
|
|
|
|
|
imply DM_SERIAL
|
|
|
|
|
imply DM_SPI
|
|
|
|
|
imply DM_SPI_FLASH
|
|
|
|
|
imply DM_USB
|
|
|
|
|
imply DM_VIDEO
|
|
|
|
|
imply SYSRESET
|
|
|
|
|
imply SYSRESET_X86
|
|
|
|
|
imply USB_ETHER_ASIX
|
|
|
|
|
imply USB_ETHER_SMSC95XX
|
|
|
|
|
imply USB_HOST_ETHER
|
|
|
|
|
|
|
|
|
|
config XTENSA
|
|
|
|
|
bool "Xtensa architecture"
|
|
|
|
|
select CREATE_ARCH_SYMLINK
|
|
|
|
|
select SUPPORT_OF_CONTROL
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
|
|
|
|
config SYS_ARCH
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the architecture name to build the
|
|
|
|
|
appropriate arch/<CONFIG_SYS_ARCH> directory.
|
|
|
|
|
All the architectures should specify this option correctly.
|
|
|
|
|
|
|
|
|
|
config SYS_CPU
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the CPU name to build the correct
|
|
|
|
|
arch/<CONFIG_SYS_ARCH>/cpu/<CONFIG_SYS_CPU> directory.
|
|
|
|
|
|
|
|
|
|
This is optional. For those targets without the CPU directory,
|
|
|
|
|
leave this option empty.
|
|
|
|
|
|
|
|
|
|
config SYS_SOC
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the SoC name to build the directory
|
|
|
|
|
arch/<CONFIG_SYS_ARCH>/cpu/<CONFIG_SYS_CPU>/<CONFIG_SYS_SOC>.
|
|
|
|
|
|
|
|
|
|
This is optional. For those targets without the SoC directory,
|
|
|
|
|
leave this option empty.
|
|
|
|
|
|
|
|
|
|
config SYS_VENDOR
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the vendor name of the target board.
|
|
|
|
|
If it is set and
|
|
|
|
|
board/<CONFIG_SYS_VENDOR>/common/Makefile exists, the vendor common
|
|
|
|
|
directory is compiled.
|
|
|
|
|
If CONFIG_SYS_BOARD is also set, the sources under
|
|
|
|
|
board/<CONFIG_SYS_VENDOR>/<CONFIG_SYS_BOARD> directory are compiled.
|
|
|
|
|
|
|
|
|
|
This is optional. For those targets without the vendor directory,
|
|
|
|
|
leave this option empty.
|
|
|
|
|
|
|
|
|
|
config SYS_BOARD
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the name of the target board.
|
|
|
|
|
If it is set, either board/<CONFIG_SYS_VENDOR>/<CONFIG_SYS_BOARD>
|
|
|
|
|
or board/<CONFIG_SYS_BOARD> directory is compiled depending on
|
|
|
|
|
whether CONFIG_SYS_VENDOR is set or not.
|
|
|
|
|
|
|
|
|
|
This is optional. For those targets without the board directory,
|
|
|
|
|
leave this option empty.
|
|
|
|
|
|
|
|
|
|
config SYS_CONFIG_NAME
|
|
|
|
|
string
|
|
|
|
|
help
|
|
|
|
|
This option should contain the base name of board header file.
|
|
|
|
|
The header file include/configs/<CONFIG_SYS_CONFIG_NAME>.h
|
|
|
|
|
should be included from include/config.h.
|
|
|
|
|
|
|
|
|
|
source "arch/arc/Kconfig"
|
|
|
|
|
source "arch/arm/Kconfig"
|
|
|
|
|
source "arch/m68k/Kconfig"
|
|
|
|
|
source "arch/microblaze/Kconfig"
|
|
|
|
|
source "arch/mips/Kconfig"
|
|
|
|
|
source "arch/nds32/Kconfig"
|
|
|
|
|
source "arch/nios2/Kconfig"
|
|
|
|
|
source "arch/powerpc/Kconfig"
|
|
|
|
|
source "arch/sandbox/Kconfig"
|
|
|
|
|
source "arch/sh/Kconfig"
|
|
|
|
|
source "arch/x86/Kconfig"
|
|
|
|
|
source "arch/xtensa/Kconfig"
|
|
|
|
|
source "arch/riscv/Kconfig"
|
