29 Feb, 2020
1 commit
-
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini
23 Jan, 2020
1 commit
-
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini
05 Dec, 2019
1 commit
-
Both symbols must be enabled when there is a raw NAND driver
selected. Also enable them when CONFIG_CMD_NAND is selected to avoid
breaking things when we'll further rework the MTD dependency
description.Signed-off-by: Miquel Raynal
Reviewed-by: Boris Brezillon
[trini: Rebase and migrate a few more boards here]
Signed-off-by: Tom Rini
04 Dec, 2019
1 commit
-
CONFIG_MTD must be reserved for the MTD core. Like any other
subsystem, prefix the symbol by DM when it comes to DM support.Signed-off-by: Miquel Raynal
Reviewed-by: Boris Brezillon
[trini: Add Kconfig files]
Signed-off-by: Tom Rini
21 Nov, 2019
2 commits
-
- In ARMv8 NXP Layerscape platforms we also need to make use of
CONFIG_SYS_RELOC_GD_ENV_ADDR now, do so.
- On ENV_IS_IN_REMOTE, CONFIG_ENV_OFFSET is never used, drop the define
to 0.
- Add Kconfig entry for ENV_ADDR.
- Make ENV_ADDR / ENV_OFFSET depend on the env locations that use it.
- Add ENV_xxx_REDUND options that depend on their primary option and
SYS_REDUNDAND_ENVIRONMENT
- On a number of PowerPC platforms, use SPL_ENV_ADDR not CONFIG_ENV_ADDR
for the pre-main-U-Boot environment location.
- On ENV_IS_IN_SPI_FLASH, check not for CONFIG_ENV_ADDR being set but
rather it being non-zero, as it will now be zero by default.
- Rework the env_offset absolute in env/embedded.o to not use
CONFIG_ENV_OFFSET as it was the only use of ENV_OFFSET within
ENV_IS_IN_FLASH.
- Migrate all platforms.Cc: Wolfgang Denk
Cc: Joe Hershberger
Cc: Patrick Delaunay
Cc: uboot-stm32@st-md-mailman.stormreply.com
Signed-off-by: Tom Rini
Acked-by: Joe Hershberger
Reviewed-by: Simon Goldschmidt -
Today in initr_reloc_global_data() we use some non-obvious tests to
determine if we need to relocate the env_addr within gd or not. In
order to facilitate migration of other symbols to Kconfig we need to
introduce a new symbol for this particular use case.Cc: Wolfgang Denk
Cc: Joe Hershberger
Signed-off-by: Tom Rini
13 Nov, 2019
1 commit
-
Move this symbol to Kconfig. As part of this we can drop a UBI-specific
symbol that was a stop-gap for not having this particular symbol in
Kconfig.Signed-off-by: Tom Rini
08 Nov, 2019
1 commit
-
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini
12 Apr, 2019
1 commit
-
This patch update the behavior introduced by
commit 96907c0fe50a ("dm: spi: Read default speed and mode values from DT")In case of DT boot, don't read default speed and mode for SPI from
CONFIG_* but instead read from DT node. This will make sure that boards
with multiple SPI/QSPI controllers can be probed at different
bus frequencies and SPI modes.Remove also use in boards of the value speed=0 (no more supported)
for ENV in SPI by using CONFIG_ENV_SPI_MAX_HZ=0.DT values will be always used when available (full DM support of
SPI slave with available DT node) even if speed and mode are requested;
for example in splash screen support (in splash_sf_read_raw)
or in SPL boot (in spl_spi_load_image).
The caller of spi_get_bus_and_cs() no more need to force speed=0.But the current behavior don't change if the SPI slave is not
present (device with generic driver is created automatically)
or if platdata is used (CONFIG_OF_PLATDATA).Signed-off-by: Patrick Delaunay
Acked-by: Jagan Teki
26 Mar, 2019
1 commit
-
This converts the following to Kconfig:
CONFIG_ENV_SPI_BUS
CONFIG_ENV_SPI_CS
CONFIG_ENV_SPI_MAX_HZ
CONFIG_ENV_SPI_MODEMost of time these value are not needed, CONFIG_SF_DEFAULT
with same value is used, so I introduced CONFIG_USE_ENV_SPI_*
to force the associated value for the environment.Signed-off-by: Patrick Delaunay
24 Jan, 2019
1 commit
-
Now that network support is added for the ocelot platform, let's add it
in the default configuration.Signed-off-by: Gregory CLEMENT
19 Jan, 2019
1 commit
-
Rsync all defconfig files using moveconfig.py
Signed-off-by: Tom Rini
16 Jan, 2019
2 commits
-
This enables the use of the MSCC serial GPIO driver to control the
LEDs on the MSCC VCoreIII 'ocelot' pcb123 and pcb120.Signed-off-by: Lars Povlsen
-
As we are moving to multi-dtb and board detection, remove static board
config options, and introduce board probing instead.Luton: This add single-binary support for the two MSCC luton-based
reference boards - pcb090 and pcb091. The SoC chip ID is used to
determine the board type.Ocelot: This add single-binary support for the two MSCC ocelot-based
reference boards - pcb120 and pcb123. The PHY ids on specific ports
are used to determine the board type.Signed-off-by: Lars Povlsen
19 Dec, 2018
1 commit
-
Adding the support for 2 boards sharing common code for Ocelot chip:
PCB120 and PCB123Signed-off-by: Gregory CLEMENT