kconfig: arm: introduce symbol for ARM CPUsThis commit introduces a Kconfig symbol for each ARM CPU:CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,CPU_ARM1176, CPU_V7, CPU_PXA
kconfig: arm: introduce symbol for ARM CPUsThis commit introduces a Kconfig symbol for each ARM CPU:CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,CPU_ARM1176, CPU_V7, CPU_PXA, CPU_SA1100.Also, it adds the CPU feature Kconfig symbol HAS_VBAR which is selectedfor CPU_ARM1176 and CPU_V7.For each target, the corresponding CPU is selected and the definition ofSYS_CPU in the corresponding Kconfig file is removed.Also, it removes redundant "string" type in some Kconfig files.Signed-off-by: Georges Savoundararadj <savoundg@gmail.com>Acked-by: Albert ARIBAUD <albert.u.boot@aribaud.net>Cc: Masahiro Yamada <yamada.m@jp.panasonic.com>
show more ...
kconfig: remove redundant "string" type in arch and board KconfigsNow the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}are specified in arch/Kconfig.We can delete the ones in
kconfig: remove redundant "string" type in arch and board KconfigsNow the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}are specified in arch/Kconfig.We can delete the ones in arch and board Kconfig files.This commit can be easily reproduced by the following command:find . -name Kconfig -a ! -path ./arch/Kconfig | xargs sed -i -e '/config[[:space:]]SYS_\(ARCH\|CPU\|SOC\|\VENDOR\|BOARD\|CONFIG_NAME\)/ { N s/\n[[:space:]]*string//}'Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
Add board MAINTAINERS filesWe have switched to Kconfig and the boards.cfg file is going tobe removed. We have to retrieve the board status and maintainersinformation from it.The MAINTAINERS for
Add board MAINTAINERS filesWe have switched to Kconfig and the boards.cfg file is going tobe removed. We have to retrieve the board status and maintainersinformation from it.The MAINTAINERS format as in Linux Kernel would be nicebecause we can crib the scripts/get_maintainer.pl script.After some discussion, we chose to put a MAINTAINERS file under eachboard directory, not the top-level one because we want to collectrelevant information for a board into a single place.TODO:Modify get_maintainer.pl to scan multiple MAINTAINERS files.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Suggested-by: Tom Rini <trini@ti.com>Acked-by: Simon Glass <sjg@chromium.org>
kconfig: add board Kconfig and defconfig filesThis commit adds: - arch/${ARCH}/Kconfig provide a menu to select target boards - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
kconfig: add board Kconfig and defconfig filesThis 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 scriptbased on boards.cfg)In Linux Kernel, defconfig files are located underarch/${ARCH}/configs/ directory.It works in Linux Kernel since ARCH is always given from thecommand 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 asingle directory ./configs/.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Acked-by: Simon Glass <sjg@chromium.org>
board: arm: convert makefiles to Kbuild styleSigned-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>Cc: Andreas Bießmann <andreas.devel@googlemail
board: arm: convert makefiles to Kbuild styleSigned-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>Cc: Andreas Bießmann <andreas.devel@googlemail.com>Cc: Stefano Babic <sbabic@denx.de>Cc: Prafulla Wadaskar <prafulla@marvell.com>Cc: Minkyu Kang <mk7.kang@samsung.com>Cc: Vipin Kumar <vipin.kumar@st.com>Cc: Tom Warren <twarren@nvidia.com>Cc: Tom Rini <trini@ti.com>
ARM: mxs: Receive r0 and r1 passed from BootROMMake sure value in register r0 and r1 is preserved and passed tothe board_init_ll() and mxs_common_spl_init() where it can beprocessed further. The
ARM: mxs: Receive r0 and r1 passed from BootROMMake sure value in register r0 and r1 is preserved and passed tothe board_init_ll() and mxs_common_spl_init() where it can beprocessed further. The value in r0 can be configured during theBootStream generation to arbitary value, r1 contains pointer toreturn value from CALL'd function.This patch also clears the value in r0 before returning to BootROMto make sure the BootROM is not confused by this value.Finally, this patch cleans up some comments in the start.S file.Signed-off-by: Marek Vasut <marex@denx.de>Cc: Fabio Estevam <fabio.estevam@freescale.com>Cc: Stefano Babic <sbabic@denx.de>
Add GPL-2.0+ SPDX-License-Identifier to source filesSigned-off-by: Wolfgang Denk <wd@denx.de>[trini: Fixup common/cmd_io.c]Signed-off-by: Tom Rini <trini@ti.com>
mx23evk: Add splash screen supportEnable display support.Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
mx23evk: Do not set voltage selection bit for SSP padsmx23 SSP pad registers do not contain voltage selection bit, so just remove it.Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
mx23evk: Fix DDR pin iomux settingsChange MUX_CONFIG_EMI to use the same drive strength as the bootlets code fromFreescale, which results in much better stability.Signed-off-by: Fabio Estevam <f
mx23evk: Fix DDR pin iomux settingsChange MUX_CONFIG_EMI to use the same drive strength as the bootlets code fromFreescale, which results in much better stability.Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
mx23evk: Adjust DRAM control register to use full 128MB of RAMAdjust HW_DRAM_CTL14 to enable the chip selects to allow usage of full128MB of RAM.Signed-off-by: Otavio Salvador <otavio@ossystems.
mx23evk: Adjust DRAM control register to use full 128MB of RAMAdjust HW_DRAM_CTL14 to enable the chip selects to allow usage of full128MB of RAM.Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
mx23evk: Add initial board supportThe following features are supported: * 128 MB DDR1 SDRAM * DUART * SD/MMC Card SocketSigned-off-by: Otavio Salvador <otavio@ossystems.com.br>Tested-by: Fabi
mx23evk: Add initial board supportThe following features are supported: * 128 MB DDR1 SDRAM * DUART * SD/MMC Card SocketSigned-off-by: Otavio Salvador <otavio@ossystems.com.br>Tested-by: Fabio Estevam <fabio.estevam@freescale.com>