Move from CONFIG_SYS_EXTRA_OPTIONS to Kconfig option.
Signed-off-by: NYork Sun <york.sun@nxp.com>

Move from CONFIG_SYS_EXTRA_OPTIONS to Kconfig option.
Signed-off-by: NYork Sun <york.sun@nxp.com>

Move from CONFIG_SYS_EXTRA_OPTIONS to Kconfig option.
Signed-off-by: NYork Sun <york.sun@nxp.com>

Now all mpc85xx and mpc86xx have converted to use SYS_CCSRBAR_DEFAULT
in Kconfig. Drop this macro for LSCH2 and remove from white list.
Signed-off-by: NYork Sun <york.sun@nxp.com>

Move default value definitions to Kconfig SYS_CCSRBAR_DEFAULT.
Signed-off-by: NYork Sun <york.sun@nxp.com>

Move default value definitions to to Kconfig SYS_CCSRBAR_DEFAULT.
Signed-off-by: NYork Sun <york.sun@nxp.com>

Instead of using EXTRA options in defconfig, use two targets
in Kconfig to select correct SoC.
Signed-off-by: NYork Sun <york.sun@nxp.com>

The catch-all job is failing due to time limits depending on factors out
of our control, so move Samsung and Rockchip boards into their own jobs
and then exclude them from the general ARM and AArch64 jobs.
Signed-off-by: NTom Rini <trini@konsulko.com>

Before disable cache, need to first flush cache.

There maybe dirty data in D-Cache before disable D-Cache.
After disable D-Cache, the first store instructions in
psci_v7_flush_dcache_all will directly store registers
{r4-r5, r7, r9-r11, lr} to memory.
If there is dirty data before disable D-Cache,
psci_v7_flush_dcache_all will flush data to memory,
and may overwrite the memory that hold the registers
{r4-r5, r7, r9-r11, lr}.

So before disable cache, first flush D-Cache.
Signed-off-by: NPeng Fan <peng.fan@nxp.com>
Cc: Albert Aribaud <albert.u.boot@aribaud.net>
Cc: Chen-Yu Tsai <wens@csie.org>
Cc: Hans de Goede <hdegoede@redhat.com>
Cc: Hongbo Zhang <hongbo.zhang@nxp.com>
Cc: York Sun <york.sun@nxp.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>
Cc: Tom Rini <trini@konsulko.com>

Juno uses a 1:1 mapping between CPU and PCI addresses for IO. First,
that will trip devices that cannot use more than 16 bits of addresses
for IO, second it is un-necessary as the system can handle zero-based
PCI addresses just fine.

Change the mapping to start IO bus addresses from zero.
Signed-off-by: NLiviu Dudau <Liviu.Dudau@foss.arm.com>

Firmware provides a spin table on the raspberry pi. This table shouldn't
get overwritten by payloads, so we need to mark it as reserved.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Acked-by: NStephen Warren <swarren@wwwdotorg.org>

To enable working efifb support, let's map the frame buffer as 32bpp
instead of 16bpp.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Acked-by: NStephen Warren <swarren@wwwdotorg.org>

The rpi has a pretty simple way of resetting the whole system. All it takes
is to poke a few registers at a well defined location in MMIO space.

This patch adds support for the EFI loader implementation to allow an OS to
reset and power off the system when we're outside of boot time.
Signed-off-by: NAlexander Graf <agraf@suse.de>

Add support to detect RGMII link interface from link-interface
device tree entry. Also rename the existing link type enums so
that it provides meaningful interface like SGMII.
Signed-off-by: NMugunthan V N <mugunthanvnm@ti.com>
Reported-by: NSekhar Nori <nsekhar@ti.com>
Tested-by: NSekhar Nori <nsekhar@ti.com>
Acked-by: NJoe Hershberger <joe.hershberger@ni.com>

This patch removes use of U_BOOT_DEVICE in board/raspberrypi/rpi/rpi.c,
enables OF_CONTROL in the config and adjusts the rpi_*defconfig configs.
Signed-off-by: NFabian Vogt <fvogt@suse.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

When using OF_CONTROL, the disabled value of the mini UART platdata
gets reset after board_early_init_f. So move detection and disabling
to board_init and remove board_early_init_f.
This uses the first device using the mini uart driver, as this method
works reliably with different device trees or even no device tree at all.
Signed-off-by: NFabian Vogt <fvogt@suse.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

For the Raspberry Pi 3 it needs to be possible to disable the serial
device after initialization happens, as only after the GPIO device is available
it is known whether the mini uart is usable.
Signed-off-by: NFabian Vogt <fvogt@suse.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

The information currently set via platdata has to be represented in the
device tree now. bcm283x-uboot.dtsi adds the u-boot specific "skip-init"
property to the serial nodes and enables initialization in the pre-reloc phase.

Cc: Albert Aribaud <albert.u.boot@aribaud.net>
Signed-off-by: NFabian Vogt <fvogt@suse.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

This patch adds device trees for the bcm283x platform to be used with
OF_CONTROL. The version 4.8-rc7 of the linux kernel was used as source.

Cc: Albert Aribaud <albert.u.boot@aribaud.net>
Signed-off-by: NFabian Vogt <fvogt@suse.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

This patch adds dt-bindings as used by the linux kernel device trees
for the bcm283x family.

Albert Aribaud <albert.u.boot@aribaud.net>
Signed-off-by: NFabian Vogt <fvogt@suse.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

To be able to represent the skip-init platdata element with OF_CONTROL,
it needs to be read from the device tree as well and put into the platform data.

Cc: Eric Anholt <eric@anholt.net>
Signed-off-by: NFabian Vogt <fvogt@suse.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

This patch adds device tree support for the bcm283x mini-uart driver.
Signed-off-by: NFabian Vogt <fvogt@suse.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

This patch adds device tree support for the bcm2835 GPIO driver.
Signed-off-by: NFabian Vogt <fvogt@suse.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

fill_dir_slot use get_contents_vfatname_block as a temporary buffer for
constructing a list of dir_slot entries. To save the memory and providing
correct type of memory for above usage, a local buffer with accurate size
declaration is introduced.

The local array size 640 is used because for long file name entry,
each entry use 32 bytes, one entry can store up to 13 characters.
The maximum number of entry possible is 20. So, total size is
32*20=640bytes.
Signed-off-by: NGenevieve Chan <ccheauya@altera.com>
Signed-off-by: NTien Fong Chee <tfchee@altera.com>

Introduce USB Gadget config option. This allows to combine Makefile
entries for SPL_USBETH_SUPPORT and SPL_DFU_SUPPORT.
Signed-off-by: NStefan Agner <stefan.agner@toradex.com>
Acked-by: NLukasz Majewski <l.majewski@samsung.com>
Tested-by: NRavi Babu <ravibabu@ti.com>

The DFU Kconfig menu entries should be part of the SPL
Kconfig file. Also avoid using the top level Makefile by
moving the config dependent build artifacts to the driver/
and driver/usb/gadget/ Makfiles.

With that, DFU can be built again in SPL if
CONFIG_SPL_DFU_SUPPORT is enabled.

Fixes: 6ad61022 ("usb:gadget: Disallow DFU in SPL for now")
Signed-off-by: NStefan Agner <stefan.agner@toradex.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Acked-by: NLukasz Majewski <l.majewski@samsung.com>

Some devices (e.g. dra7xx) support loading to RAM using DFU without
having direct boot from RAM support. Make sure the linker list
does not contain BOOT_DEVICE_RAM if CONFIG_SPL_RAM_DEVICE is not
enabled.

Fixes: 98136b2f ("spl: Convert spl_ram_load_image() to use linker list")
Signed-off-by: NStefan Agner <stefan.agner@toradex.com>
Acked-by: NLukasz Majewski <l.majewski@samsung.com>

The actual define symbol is FAT_ENV_DEVICE_AND_PART
Signed-off-by: NNicolae Rosia <Nicolae_Rosia@Mentor.com>

This fixes the loop delay when using a hw watchdog.

In case a watchdog is used that accesses CPU registers,
the defined delay of 20us in a tight loop will cause a
huge delay in the actual timeout seen. This is caused
by the fact that udelay will inheritantly call WATCHDOG_RESET.
Together with the omap wdt implementation, the seen timeout increases up to
around 30s. This makes the loop very slow and causes long
delays when using the modem.

Instead, implement the 2 sec loop by using the timer interface to know
when to break out of the timeout loop. Watchdog kicking is taken care of
by getc().
Signed-off-by: NTomas Melin <tomas.melin@vaisala.com>

Commit d97dc8a0 separated the non-command code into its own file
which caused variable sata_curr_device can not be set to a correct
value.

Before commit d97dc8a0, variable sata_curr_device can be set
correctly in sata_initialize().
After commit d97dc8a0, sata_initialize() is moved out to its own file.
Accordingly, variable sata_curr_device is removed from sata_initialize()
too. This caused sata_curr_device never gets a chance to be set properly
which prevent other commands from being executed.

This patch sets variable sata_curr_device properly.

Fixes: d97dc8a0 (dm: sata: Separate the non-command code into its
 own file)
Signed-off-by: NTang Yuantian <yuantian.tang@nxp.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

commit 183923d3 enforces that the
environment must start at an erase block boundary.

For block devices the sample fw_env.config does not mandate a erase block size
for block devices. A missing setting defaults to the full env size.

Depending on the environment location the alignment check now errors out for
perfectly legal settings.

Fix this by defaulting to the standard blocksize of 0x200 for environments
stored in a block device.
That keeps the fw_env.config files for block devices working even with that
new check.
Signed-off-by: NMax Krummenacher <max.krummenacher@toradex.com>

The Makefile in tools/ tries to find the "swig" utility by calling "which".
If nothing is found in the path, some versions of which will print an error
message:
$ make clean
which: no swig in (/usr/local/bin:/usr/bin:/bin)

This does not apply to all version of "which", though:
$ echo $0
bash
$ type which
which is aliased to `type -path'
$ which foo				<== this version is OK
$ /usr/bin/which foo			<== this one is chatty
/usr/bin/which: no foo in (/usr/local/bin:/usr/bin:/bin)
$ sh					<== make uses /bin/sh
sh-4.3$ which foo			<== no alias here
which: no foo in (/usr/local/bin:/usr/bin:/bin)

This error message is rather pointless in our case, since we just have
this very check to care for this. So add stderr redirection to suppress
the message.
Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

NFS loading support has been added to the default environment for
most boot components, as PMMC and MON loading were added later they
did not originally get the NFS commands added, add these now.
Signed-off-by: NAndrew F. Davis <afd@ti.com>
Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>

The config option TARGET_K2x_EVM is set by the k2x defconfigs to pick
a board target, but the header configs also set K2x_EVM. This config
is redundant, remove it and use TARGET_K2x_EVM everywhere in its place.
Signed-off-by: NAndrew F. Davis <afd@ti.com>
Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>

This patch fixes the warning about misaligned cache on Armada XP:

CACHE: Misaligned operation at range [7ffff000, 7fffffac]
Signed-off-by: NStefan Roese <sr@denx.de>
Cc: Valentin Longchamp <valentin.longchamp@keymile.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

Commit c68c62 ("i2c: mvtwsi: Make delay times frequency-dependent")
extensively used the ndelay function with a calculated parameter
which is dependant on the configured frequency of the I2C bus. If
standard speed is employed, the parameter is usually 10000 (10000ns
period length for 100kHz frequency).

But, since the arm architecture does not implement a proper version of
ndelay, the fallback default from include/linux/compat.h is used,
which defines every ndelay as udelay(1). This causes problems for
slower speeds on arm, since the delay time is now 9us too short for
the desired frequency, which leads to random failures of the I2C
interface.

To remedy this, we implement a proper, parameter-aware ndelay fallback
for architectures that don't implement a real ndelay function.
Reported-By: NJason Brown <Jason.brown@apcon.com>
To: Tom Rini <trini@konsulko.com>
To: Heiko Schocher <hs@denx.de>
Signed-off-by: NMario Six <mario.six@gdsys.cc>

remove now unused CONFIG_TRDX_PID_XXX
Signed-off-by: NMarcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: NStefan Agner <stefan.agner@toradex.com>
Acked-by: NMax Krummenacher <max.krummenacher@toradex.com>

Now with the config block handling in place move the U-Boot environment
location before the config block at the end of 1st "boot sector" as
deployed during production using our downstream BSP.
Signed-off-by: NMarcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: NMax Krummenacher <max.krummenacher@toradex.com>

With our common code in place actually make use of it across all our
modules.
Signed-off-by: NMarcel Ziswiler <marcel.ziswiler@toradex.com>
Acked-by: NMax Krummenacher <max.krummenacher@toradex.com>