SPDX: Convert all of our single license tags to Linux Kernel styleWhen U-Boot started using SPDX tags we were among the early adopters andthere weren't a lot of other examples to borrow from. So
SPDX: Convert all of our single license tags to Linux Kernel styleWhen U-Boot started using SPDX tags we were among the early adopters andthere weren't a lot of other examples to borrow from. So we picked thearea of the file that usually had a full license text and replaced itwith an appropriate SPDX-License-Identifier: entry. Since then, theLinux Kernel has adopted SPDX tags and they place it as the very firstline in a file (except where shebangs are used, then it's second line)and with slightly different comment styles than us.In part due to community overlap, in part due to better tag visibilityand in part for other minor reasons, switch over to that style.This commit changes all instances where we have a single declaredlicense in the tag as both the before and after are identical in tagcontents. There's also a few places where I found we did not have a tagand have introduced one.Signed-off-by: Tom Rini <trini@konsulko.com>
show more ...
net: Move enetaddr env access code to env config instead of net configIn order that we can use eth_env_* even when CONFIG_NET isn't set, movethese functions to environment code from net code.Thi
net: Move enetaddr env access code to env config instead of net configIn order that we can use eth_env_* even when CONFIG_NET isn't set, movethese functions to environment code from net code.This fixes failures such as: board/ti/am335x/built-in.o: In function `board_late_init': board/ti/am335x/board.c:752: undefined reference to `eth_env_set_enetaddr' u-boot/board/ti/am335x/board.c:766: undefined reference to `eth_env_set_enetaddr'which caters for use cases such as:commit f411b5cca48f ("board: am335x: Always set eth/eth1addr environmentvariable")when Ethernet is required in Linux, but not U-Boot.Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
env: Rename eth_getenv_enetaddr() to eth_env_get_enetaddr()Rename this function for consistency with env_get().Signed-off-by: Simon Glass <sjg@chromium.org>
env: Rename eth_setenv_enetaddr() to eth_env_set_enetaddr()Rename this function for consistency with env_set().Signed-off-by: Simon Glass <sjg@chromium.org>
pengwyn: nand and ethernet fixes-> Add National instrument ethernet transceiver configuration used (DP83848)-> Change cpsw slave phy address-> modify nand configuration to use the correct ECC and
pengwyn: nand and ethernet fixes-> Add National instrument ethernet transceiver configuration used (DP83848)-> Change cpsw slave phy address-> modify nand configuration to use the correct ECC and correct nand features
net: cosmetic: Name ethaddr variables consistentlyUse "_ethaddr" at the end of variables and drop CamelCase.Make constant values actually 'const'.Signed-off-by: Joe Hershberger <joe.hershberger@
net: cosmetic: Name ethaddr variables consistentlyUse "_ethaddr" at the end of variables and drop CamelCase.Make constant values actually 'const'.Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>Acked-by: Simon Glass <sjg@chromium.org>
dm: select CONFIG_DM* optionsAs mentioned in the previous commit, adding default values in eachKconfig causes problems because it does not co-exist with the"depends on" syntax. (Please note this
dm: select CONFIG_DM* optionsAs mentioned in the previous commit, adding default values in eachKconfig 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 weconvert a driver into Driver Model, the board only works with DriverModel, i.e. CONFIG_DM must be always enabled for that board.So, using "select DM" is more suitable rather than allowing users tomodify it. Another good thing is, Kconfig warns unmet dependenciesfor "select" syntax, so we easily notice bugs.Actually, CONFIG_DM and other related options have been addedwithout consistency: some into arch/*/Kconfig, some intoboard/*/Kconfig, and some into configs/*_defconfig.This commit prefers "select" and cleans up the following issues.[1] Never use "CONFIG_DM=n" in defconfig filesIt 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, wedo 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 isweird. Instead, add "select DM" only to appropriate boards, whicheventually eliminates "CONFIG_DM=n", etc.[2] Delete redundant CONFIGsSandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it againin configs/sandbox_defconfig.Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig anddefines it also in omap3_beagle_defconfig and devkit8000_defconfig.Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
kconfig: remove unneeded dependency on !SPL_BUILDNow CONFIG_SPL_BUILD is not defined in Kconfig, so"!depends on SPL_BUILD" and "if !SPL_BUILD" are redundant.Signed-off-by: Masahiro Yamada <yamad
kconfig: remove unneeded dependency on !SPL_BUILDNow CONFIG_SPL_BUILD is not defined in Kconfig, so"!depends on SPL_BUILD" and "if !SPL_BUILD" are redundant.Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
dm: omap3: Move driver model CONFIGs to KconfigRemove driver model CONFIGs from the board config headers and use Kconfiginstead.Signed-off-by: Simon Glass <sjg@chromium.org>
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>
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>
am335x: Switch to CONFIG_SKIP_LOWLEVEL_INIT from guarding SPL or NOR_BOOTIn the case of SPL or NOR_BOOT (no SPL involved) we need to includecertain code in the build. Use !CONFIG_SKIP_LOWLEVEL_IN
am335x: Switch to CONFIG_SKIP_LOWLEVEL_INIT from guarding SPL or NOR_BOOTIn the case of SPL or NOR_BOOT (no SPL involved) we need to includecertain code in the build. Use !CONFIG_SKIP_LOWLEVEL_INIT rather thanCONFIG_SPL_BUILD || CONFIG_NOR_BOOT to make the code clearer, and tomake supporting XIP QSPI boot clearer in the code.Signed-off-by: Tom Rini <trini@ti.com>Reviewed-by: Wolfgang Denk <wd@denx.de>
drivers: net: cpsw: add support to have phy address from cpsw platform dataSome platforms like AM437x have different EVMs with different phy addresses,so this patch adds support for passing phy ad
drivers: net: cpsw: add support to have phy address from cpsw platform dataSome platforms like AM437x have different EVMs with different phy addresses,so this patch adds support for passing phy address via cpsw plaform data.Also renamed phy_id to phy_addr so better understanding of the code.Reviewed-by: Felipe Balbi <balbi@ti.com>Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>[trini: Update BuR am335x_igep0033 pcm051_rev3 pcm051_rev1 cm_t335pengwyn boards]Signed-off-by: Tom Rini <trini@ti.com>
am335x: Initial support for Silica Pengwyn boardThis patch add support for the Silica Pengwyn board [1]The board is based on a TI AM3354 CPU [2]All jumpers removed it will boot from the SDcard, t
am335x: Initial support for Silica Pengwyn boardThis patch add support for the Silica Pengwyn board [1]The board is based on a TI AM3354 CPU [2]All jumpers removed it will boot from the SDcard, the console is onUART1 accessible via the FDTI -> USB. The on board NAND flash issupported and can act as boot medium, depending on jumper settings.USB Host, USB Device and Ethernet are also provided but untested.[1]http://www.silica.com/product/silica-pengwyn-board.html[2]http://www.ti.com/product/am3354Signed-off-by: Lothar Felten <lothar.felten@gmail.com>[trini: Move CONFIG_BOARD_LATE_INIT into am335x_evm.h, drop unusedspi0_pin_mux from Pengwyn support]Signed-off-by: Tom Rini <trini@ti.com>