04 Mar, 2020
1 commit
-
Add initial support for the ABB SECU board, which is an ArriaV-based
SoCFPGA system with ethernet and booting from Denali NAND.Signed-off-by: Holger Brunck
Cc: Ley Foon Tan
Cc: Simon Goldschmidt
23 Jan, 2020
8 commits
-
This target is out of maintenance and can be removed.
Signed-off-by: Holger Brunck
CC: Valentin Longchamp
CC: Stefan Roese
Reviewed-by: Stefan Roese -
This target is out of maintenance and can be removed.
Signed-off-by: Holger Brunck
CC: Valentin Longchamp
CC: Stefan Roese
Reviewed-by: Stefan Roese -
This board is similar to SUV31, but the FPGA is reset concept is quite
different.Signed-off-by: Holger Brunck
CC: Valentin Longchamp
CC: Stefan Roese
Reviewed-by: Stefan Roese -
This patch adds the possibility in both debug and ramfs modes to
optionally load an env file from /tftpboot/$tftppath (this is ignored if
not present, so the change is backward compatible). This gives the debug
and ramfs scripts the possibility to set uboot environment variables
that were previously asked the users to manually set (nfs path in debug
and rootfs size in ramfs).Signed-off-by: Holger Brunck
CC: Tom Rini -
The tftppath was not set in case of run ramfs. It worked only by chance
if was already set before.Also check the boardname before setting the tftppath for COGE5.
Signed-off-by: Holger Brunck
CC: Tom Rini -
The CPUWD reset reason is used for kmp204x.
And the qrio cpu reset request is configured to operate in
core reset mode.
But for the evaluation of the qrio's reset reason register
the CPUWD figures as a unit reset source rather than a core
reset source. This patch defines the CPUWD reset as a core
reset source when evaluating the reset reason register.Signed-off-by: Rainer Boschung
CC: Priyanka Jain -
This patch moves the qrio and i2c deblocking code to
keymile/common as it will also be used by the upcoming CENT2 board.Signed-off-by: Holger Brunck
CC: Priyanka Jain -
This prevents the board from booting which is not the expected behavior.
Signed-off-by: Valentin Longchamp
Signed-off-by: Holger Brunck
CC: Priyanka Jain
18 Jan, 2020
2 commits
-
These functions relate to setting up the device tree for booting the OS.
The fdt_support.h header file supports similar functions, so move these
there.Signed-off-by: Simon Glass
-
This is a network function so let's move it into that header.
Signed-off-by: Simon Glass
10 Jan, 2020
3 commits
-
This target is out of maintenance and can be removed.
Signed-off-by: Holger Brunck
CC: Stefan Roese
CC: Valentin Longchamp
Reviewed-by: Stefan Roese -
For upcoming SECU board we have different MAC address offsets depending
on which functional unit we are running. In this case we need to pass
this value to the ivm_populate_env function instead of using the hard
coded config option there.Signed-off-by: Holger Brunck
CC: Stefan Roese
CC: Valentin Longchamp
CC: Marek Vasut
Reviewed-by: Stefan Roese -
This patch only fixes a typo.
Signed-off-by: Holger Brunck
CC: Stefan Roese
CC: Valentin Longchamp
Reviewed-by: Stefan Roese
23 Dec, 2019
2 commits
-
We can use the existing CONFIG_SYS_CONFIG_NAME define for that and
remove the option. Also fix the boot string for all km83xx boards.Signed-off-by: Holger Brunck
Reviewed-by: Priyanka Jain
CC: Priyanka Jain
CC: Valentin Longchamp -
Remove this from the board header files and move it to Kconfig. Also use
the correct default address for kmtegr1.Signed-off-by: Holger Brunck
Reviewed-by: Priyanka Jain
CC: Priyanka Jain
CC: Valentin Longchamp
03 Dec, 2019
2 commits
-
This function can be dropped when all boards use driver model for PCI. For
now, move it into init.h with a comment.Signed-off-by: Simon Glass
Reviewed-by: Tom Rini -
A number of board function belong in init.h with the others. Move them.
Signed-off-by: Simon Glass
Reviewed-by: Tom Rini
13 Aug, 2019
1 commit
-
- Various improvements to Keymile boards - mostly DT conversation
(Pascal & Holger)
- Removal of now unsupported Keymile boards (Pascal & Holger)
- Small MVEBU PCI fix (Marek)
- Turris Omnia defconfig update (Marek)
- Misc Allied Telesis defconfig updates (Chris)
12 Aug, 2019
8 commits
-
This board is unmaintained and can be removed. This also allows us to
remove kmp204x-common.h and integrate it in kmp204x.h.Signed-off-by: Valentin Longchamp
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
Signed-off-by: Valentin Longchamp
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
Remove the PORTL2 board and all its dependencies as it is no longer
supported by the company.Signed-off-by: Pascal Linder
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
Activate the driver model for the Ethernet interface (RGMII) in the KM
Kirkwood Kconfig file. Additionally, raise the auto negotiation timeout
to eight seconds as more time is required for those boards.Signed-off-by: Pascal Linder
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
Activate the driver model for the serial interface in the KM Kirkwood
Kconfig file. The associated preprocessor definitions could be removed
from the header file. However, the clock of 200 MHz needs to be declared
in the device tree.Signed-off-by: Pascal Linder
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
After moving the KM specific configurations to Kconfig, the associated
preprocessor definitions can now be removed in the headers. Moreover, the
whitelist has been adapted correspondingly.Signed-off-by: Pascal Linder
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
To execute the conversion away from board specific header files, Kconfig
menus have been implemented for all KM boards and additionally for those
having an ARM architecture.For the moment, the preprocessor definitions stay in the headers. The
boolean types, however, needed a modification (#define CONFIG_* 1).The default configuration files of some boards required an update in order
to not change the currently defined values of the configurations.Signed-off-by: Pascal Linder
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
Move env_set() over to the new header file.
Acked-by: Joe Hershberger
Signed-off-by: Simon Glass
11 Jul, 2019
4 commits
-
KM Kirkwood boards now implement the driver model for its SPI flash
interface. Therefore, the old board specific claim and release functions
can be deleted. The preprocessor definition CONFIG_SYS_KW_SPI_MPP is yet
unused as well. All its appearances and dependencies are removed in the
kirkwood_spi driver, header files and finally the configuration whitelist.Signed-off-by: Pascal Linder
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
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
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
As the SPI NOR and NAND devices share the same hardware pins, the MPP
configuration has to be changed when claiming/releasing the bus. The
current configuration is saved when claiming and restored when releasing.
Furthermore, a general-purpose output is used to switch the chip-select
signal. This is now also implemented for the DM part of the kirkwood_spi
driver.Signed-off-by: Pascal Linder
Signed-off-by: Holger Brunck
Signed-off-by: Stefan Roese -
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
Signed-off-by: Holger Brunck
Cc: Mario Six
Cc: Prabhakar Kushwaha
Signed-off-by: Stefan Roese
06 Jun, 2019
1 commit
-
Signed-off-by: Holger Brunck
21 May, 2019
1 commit
-
CONFIG_SYS_DDR_BASE is specific to mpc83xx an is always set to the same
value as CONFIG_SYS_SDRAM_BASE. Just use CONFIG_SYS_SDRAM_BASE instead.Signed-off-by: Mario Six
20 May, 2019
5 commits
-
The kmeter1, and kmcoge5ne boards also build from the same config
file with #ifdef logic.Create a separate include config for each board with the #ifdef logic
resolved as needed.Signed-off-by: Mario Six
-
The kmsupx5, tuge1, kmopti2, and kmtepr2 boards all build from the same
include config file with lots of #ifdef logic.To ease Kconfig migration, create new config include files for these
boards, and resolve the #ifdef logic as needed.Signed-off-by: Mario Six
-
The kmtegr1, kmvect1, and suvd3 boards all use the same config include
file with lots of #ifdefs in it.The Kconfig migation will become easier if we get rid of these #ifdefs
first.Hence, create distinct config include files for these boards, and unwind
the #ifdef logic in these config files to only include the options
necessary for each board.Signed-off-by: Mario Six
-
Replace CONFIG_MPC836* with proper CONFIG_ARCH_MPC836* Kconfig options.
Signed-off-by: Mario Six
-
Replace CONFIG_MPC830* with proper CONFIG_ARCH_MPC830* Kconfig options.
Signed-off-by: Mario Six
07 May, 2018
1 commit
-
When U-Boot started using SPDX tags we were among the early adopters and
there weren't a lot of other examples to borrow from. So we picked the
area of the file that usually had a full license text and replaced it
with an appropriate SPDX-License-Identifier: entry. Since then, the
Linux Kernel has adopted SPDX tags and they place it as the very first
line 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 visibility
and in part for other minor reasons, switch over to that style.This commit changes all instances where we have a single declared
license in the tag as both the before and after are identical in tag
contents. There's also a few places where I found we did not have a tag
and have introduced one.Signed-off-by: Tom Rini
28 Apr, 2018
1 commit
-
We have a large number of places where while we historically referenced
gd in the code we no longer do, as well as cases where the code added
that line "just in case" during development and never dropped it.Signed-off-by: Tom Rini