u-boot-brain/board/keymile/km_arm/Kconfig

if TARGET_KM_KIRKWOOD

config SYS_BOARD
	default "km_arm"

config SYS_VENDOR
	default "keymile"

config SYS_CONFIG_NAME
	default "km_kirkwood"

config BOARD_SPECIFIC_OPTIONS # dummy
	def_bool y
	select BOARD_LATE_INIT
	select DM
	select DM_SPI
	select DM_SPI_FLASH
	imply CMD_CRAMFS
	imply CMD_DIAG
	imply FS_CRAMFS

endif
kconfig: add board Kconfig and defconfig files This commit adds: - arch/${ARCH}/Kconfig provide a menu to select target boards - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig set CONFIG macros to the appropriate values for each board - configs/${TARGET_BOARD}_defconfig default setting of each board (This commit was automatically generated by a conversion script based on boards.cfg) In Linux Kernel, defconfig files are located under arch/${ARCH}/configs/ directory. It works in Linux Kernel since ARCH is always given from the command line for cross compile. But in U-Boot, ARCH is not given from the command line. Which means we cannot know ARCH until the board configuration is done. That is why all the "*_defconfig" files should be gathered into a single directory ./configs/. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: Simon Glass <sjg@chromium.org> 2014-07-30 14:08:14 +09:00			`if TARGET_KM_KIRKWOOD`

			`config SYS_BOARD`
			`default "km_arm"`

			`config SYS_VENDOR`
			`default "keymile"`

			`config SYS_CONFIG_NAME`
			`default "km_kirkwood"`

km: modify Kconfig file organization for KM boards As preparation for the upcoming transferring of configurations from header files to Kconfig, a common Kconfig file for all KM boards was created. For the moment, it only sources the other three, more specific, Kconfig files. Therefore, the architecture Kconfig files now include the common Kconfig file. Also, the configuration selection for KM boards was moved from the architecture Kconfig files to the board specific Kconfig files. Signed-off-by: Pascal Linder <pascal.linder@edu.hefr.ch> Signed-off-by: Holger Brunck <holger.brunck@ch.abb.com> Cc: Mario Six <mario.six@gdsys.cc> Cc: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com> Signed-off-by: Stefan Roese <sr@denx.de> 2019-06-18 20:27:47 +09:00			`config BOARD_SPECIFIC_OPTIONS # dummy`
			`def_bool y`
			`select BOARD_LATE_INIT`
km/spi: activate driver model for SPI flash on KM Kirkwood boards The corresponding configurations are selected in the common Kconfig file. This is easier than changing every affected board default configuration file. The default configuration for the PORTL2 board, however, still needs some modifications to correctly use the driver model. Signed-off-by: Pascal Linder <pascal.linder@edu.hefr.ch> Signed-off-by: Holger Brunck <holger.brunck@ch.abb.com> Signed-off-by: Stefan Roese <sr@denx.de> 2019-06-18 15:42:59 +09:00			`select DM`
			`select DM_SPI`
			`select DM_SPI_FLASH`
km: modify Kconfig file organization for KM boards As preparation for the upcoming transferring of configurations from header files to Kconfig, a common Kconfig file for all KM boards was created. For the moment, it only sources the other three, more specific, Kconfig files. Therefore, the architecture Kconfig files now include the common Kconfig file. Also, the configuration selection for KM boards was moved from the architecture Kconfig files to the board specific Kconfig files. Signed-off-by: Pascal Linder <pascal.linder@edu.hefr.ch> Signed-off-by: Holger Brunck <holger.brunck@ch.abb.com> Cc: Mario Six <mario.six@gdsys.cc> Cc: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com> Signed-off-by: Stefan Roese <sr@denx.de> 2019-06-18 20:27:47 +09:00			`imply CMD_CRAMFS`
			`imply CMD_DIAG`
			`imply FS_CRAMFS`

kconfig: add board Kconfig and defconfig files This commit adds: - arch/${ARCH}/Kconfig provide a menu to select target boards - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig set CONFIG macros to the appropriate values for each board - configs/${TARGET_BOARD}_defconfig default setting of each board (This commit was automatically generated by a conversion script based on boards.cfg) In Linux Kernel, defconfig files are located under arch/${ARCH}/configs/ directory. It works in Linux Kernel since ARCH is always given from the command line for cross compile. But in U-Boot, ARCH is not given from the command line. Which means we cannot know ARCH until the board configuration is done. That is why all the "*_defconfig" files should be gathered into a single directory ./configs/. Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com> Acked-by: Simon Glass <sjg@chromium.org> 2014-07-30 14:08:14 +09:00			`endif`