There are a few options which use lower case. We should use upper case for
all CONFIG options.
Signed-off-by: NSimon Glass <sjg@chromium.org>
[trini: Add usbtty/nand hunk to include/configs/spear3xx_evb.h]
Signed-off-by: NTom Rini <trini@konsulko.com>

A few boards define this in a header file which is incorrect. It means that
Kconfig options that rely on this cannot be used. Move it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

A few boards define this in a header file which is incorrect. It means that
Kconfig options that rely on this cannot be used. Move it.

Note that quite a few boards defined this options but do not appear to
actually use SPL:

	BSC9132QDS_NOR_DDRCLK100_SECURE
	BSC9132QDS_NOR_DDRCLK133_SECURE
	BSC9132QDS_SDCARD_DDRCLK100_SECURE
	BSC9132QDS_SDCARD_DDRCLK133_SECURE
	BSC9132QDS_SPIFLASH_DDRCLK100_SECURE
	BSC9132QDS_SPIFLASH_DDRCLK133_SECURE
	C29XPCIE_NOR_SECBOOT
	P1010RDB-PA_36BIT_NAND_SECBOOT
	P1010RDB-PA_36BIT_SPIFLASH_SECBOOT
	P1010RDB-PA_NAND_SECBOOT
	P1010RDB-PA_NOR_SECBOOT
	P1010RDB-PB_36BIT_NOR_SECBOOT
	P1010RDB-PB_36BIT_SPIFLASH_SECBOOT
	P1010RDB-PB_NAND_SECBOOT
	P1010RDB-PB_NOR_SECBOOT
	P3041DS_SECURE_BOOT
	P4080DS_SECURE_BOOT
	P5020DS_NAND_SECURE_BOOT
	P5040DS_SECURE_BOOT
	T1023RDB_SECURE_BOOT
	T1024QDS_DDR4_SECURE_BOOT
	T1024QDS_SECURE_BOOT
	T1024RDB_SECURE_BOOT
	T1040RDB_SECURE_BOOT
	T1042D4RDB_SECURE_BOOT
	T1042RDB_SECURE_BOOT
	T2080QDS_SECURE_BOOT
	T2080RDB_SECURE_BOOT
	T4160QDS_SECURE_BOOT
	T4240QDS_SECURE_BOOT
	ls1021aqds_nor_SECURE_BOOT
	ls1021atwr_nor_SECURE_BOOT
	ls1043ardb_SECURE_BOOT

For these boards CONFIG_SPL_DM will no-longer be defined in SPL. But since
they apparently don't have an SPL, this should not matter.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Some of the SPL options have TPL equivalents. Add these to Kconfig so that
we can convert these options over to work from Kconfig.
Signed-off-by: NSimon Glass <sjg@chromium.org>

There are a lot of SPL options in U-Boot to enable various features and
drivers. Currently these do not use Kconfig. Add them to Kconfig along
with suitable help, and drop them from the README.
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present TPL uses the same options as SPL support. In a few cases the board
config enables or disables the SPL options depending on whether
CONFIG_TPL_BUILD is defined.

With the move to Kconfig, options are determined for the whole build and
(without a hack like an #undef in a header file) cannot be controlled in this
way.

Create new TPL options for these and update users. This will allow Kconfig
conversion to proceed for these boards.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This option does not exist in U-Boot. Drop it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

The secure boot header files incorrectly define SPL options only if
CONFIG_SPL_BUILD is defined. This means that the options are only enabled
in an SPL build, and not with a normal 'make xxx_defconfig'. This means
that moveconfig.py cannot work, since it sees the options as disabled even
when they may be manually enabled in an SPL build.

Fix this by changing the order.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Move the SPL settings into common/spl where most of the SPL code is kept.
Signed-off-by: NSimon Glass <sjg@chromium.org>

The moveconfig tool is quite clever and generally produces results that
are suitable for sending as a patch without further work. The main required
step is to add the changes to a commit.

Add an option to do this automatically. This allows moveconfig to be used
from a script to convert multiple CONFIG options, once per commit.
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present it is not easy to use moveconfig from a script since it asks
for user input a few times. Add a -y option to skip this and assume that
'y' was entered.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Update the defconfig files to match their canonical form, as produced by
'make safedefconfig'.

This is the result of running 'tools/moveconfig.py -s' on the tree.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Since the 'clk_client.h' doesn't exist, it should be 'clk.h'.
Signed-off-by: NWenyou Yang <wenyou.yang@atmel.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

The special handling of the chip address and register address must only
happen before we send the data buffer, otherwise we will end up
inserting both of these every 32 bytes.
Signed-off-by: NJohn Keeping <john@metanate.com>
Acked-by: NSimon Glass <sjg@chromium.org>

There is no point in writing intermediate values to the txdata
registers.

Also add padding to the debug logging to make it easier to read when
there are leading zeroes.
Signed-off-by: NJohn Keeping <john@metanate.com>
Acked-by: NSimon Glass <sjg@chromium.org>

Make it clear that we are using the same value in two adjacent lines.
Signed-off-by: NJohn Keeping <john@metanate.com>
Acked-by: NSimon Glass <sjg@chromium.org>

Signed-off-by: NTom Rini <trini@konsulko.com>

This patch fixes the "sf probe" command. The very first SPI flash probe
passes, for instance when u-boot tries to read its environment settings
from a (Q)SPI memory but next "sf probe" commands fail because the flash
memory node is unbound from the SPI controller children nodes.
Signed-off-by: NCyrille Pitchen <cyrille.pitchen@atmel.com>
Signed-off-by: NWenyou Yang <wenyou.yang@atmel.com>
Tested-by: NStefan Roese <sr@denx.de>
Tested-by: NHannes Schmelzer <oe5hpm@oevsv.at>
Reviewed-by: NSimon Glass <sjg@chromium.org>

move VERSION_VARIABLE from board config file into a
Kconfig option.
Signed-off-by: NHeiko Schocher <hs@denx.de>

We only need the function found in cmd/disk.c when we have IDE, SCSI or
USB_STORAGE enabled.  While the first two are easy to get right, in the
3rd case we assume that the set of cases where we do have USB and do not
enable USB_STORAGE are small enough that we can take the small bloat of
un-discarded strings on gcc prior to 6.x
Signed-off-by: NTom Rini <trini@konsulko.com>

In some cases we were missing CONFIG_USB=y so enable that when needed.
Reviewed-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: NTom Rini <trini@konsulko.com>

A previous patch (net: asix: fix operation without eeprom) added a
two-byte shift to the packet buffer when receiving a packet on the
AX88772B.

This shift was not included when the driver was updated to work with
DriverModel. Testing on a Marvell DB-88F6820-ACM showed that the adapter
was not functioning correctly (EHCI timeouts).

This patch brings the two-byte shift to the DriverModel implementation
of ops->recv (asix_eth_recv).

Testing on the same board, we were able to TFTP a file over and confirm
that the crc32 was correct.
Signed-off-by: NJoshua Scott <joshua.scott@alliedtelesis.co.nz>
Acked-by: NJoe Hershberger <joe.hershberger@ni.com>

This reverts commit 6279b49e.

This caused a bad data crc.
Signed-off-by: NJoe Hershberger <joe.hershberger@ni.com>
Reported-by: NGuillaume GARDET <guillaume.gardet@free.fr>

This reverts commit 998372b4.

This caused a data abort on some platform.
Signed-off-by: NJoe Hershberger <joe.hershberger@ni.com>
Reported-by: NGuillaume GARDET <guillaume.gardet@free.fr>

Signed-off-by: NTom Rini <trini@konsulko.com>

Update the README to add support for K2G EVM. Also
- Add steps on how to use MMC boot
- Fix load address when using CCS
- Update build target to u-boot.bin from u-boot-dtb.bin as all ks2
  platforms uses DT.
Reviewed-by: NTom Rini <trini@konsulko.com>
Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>

Provide version of struct efi_mem_desc in efi_get_memory_map().

EFI_BOOT_SERVICES.GetMemoryMap() in UEFI specification v2.6 defines
memory descriptor version to 1. Linux kernel also expects descriptor
version to be 1 and prints following warning during boot if its not:

Unexpected EFI_MEMORY_DESCRIPTOR version 0
Signed-off-by: NMian Yousaf Kaukab <yousaf.kaukab@gmail.com>

ENOLINK is not required by POSIX and does not exist on OpenBSD
and likely other systems.
Signed-off-by: NJonathan Gray <jsg@jsg.id.au>

The u-boot endian macros map directly to system endian
macros on OpenBSD.
Signed-off-by: NJonathan Gray <jsg@jsg.id.au>

When beagleboard-X15 is booted, we see the following log:
Unidentified board claims BBRDX15_ in eeprom header

This is because of the missing check for x15 (the default) and reports
an error for a valid board configuration. Fix the same.
Signed-off-by: NNishanth Menon <nm@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>
Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>

Felipe Balbi has move on from TI and the current email ID is no longer
valid. So, replacing with Lokesh.

While at it, update missing config file which was untracked.
Signed-off-by: NNishanth Menon <nm@ti.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

Line up comments for readibility.
Signed-off-by: NRobert P. J. Day <rpjday@crashcourse.ca>

Use environment variable "kernel_addr_r" to indicate the location
in RAM where FIT image will be stored.
Use label command "kernel" to indicate which <path> the FIT image at.
Signed-off-by: NWenbin Song <wenbin.song@nxp.com>

When FIT image is used, a single image provides kernel, device
tree and optionally ramdisk. Argc and argv need to be adjusted
to support this.

Test cases:
	1. Booting with legacy images
	2. Booting with legacy images without initrd
	3. Booting with FIT image
Test commands:
	1. pxe get && pxe boot
	2. sysboot
Signed-off-by: NYork Sun <york.sun@nxp.com>
Signed-off-by: NWenbin Song <wenbin.song@nxp.com>

Correct a small number of spelling mistakes.
Signed-off-by: NRobert P. J. Day <rpjday@crashcourse.ca>

As bootargs is hard-coded for the default behavior on the
omap3_pandora, only set the bootargs if distro_bootcmd fails to
load. This leaves distro_bootcmd free to use alternate boot arguments.
Signed-off-by: NVagrant Cascadian <vagrant@debian.org>

Add support for using distro_bootcmd to the omap3_pandora target,
falling back to prior behavior.
Signed-off-by: NVagrant Cascadian <vagrant@debian.org>

We are supposed to not add config entries with only "default y"
in board/SoC Kconfig files.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
Acked-by: NEnric Balletbo i Serra <enric.balletbo@collabora.com>