Update the email address for the boards that I maintain.
Signed-off-by: NSteve Rae <steve.rae@raedomain.com>

- increase the size of the fill buffer
- testing has shown a 10x improvement when the sparse image
  has large CHUNK_TYPE_FILL chunks
Signed-off-by: NSteve Rae <srae@broadcom.com>

In order to process the CHUNK_TYPE_DONT_CARE properly, there is
a requirement to be able to 'reserve' a specified number of blocks
in the storage media. Because of the special handling of "bad blocks"
in NAND devices, this is implemented in a storage abstraction function.
Signed-off-by: NSteve Rae <srae@broadcom.com>
Reviewed-by: NMaxime Ripard <maxime.ripard@free-electrons.com>

- update fastboot_okay() and fastboot_fail()

This file originally came from upstream code.

While retaining the storage abstraction feature, this is the second
set of the changes required to resync with the
  cmd_flash_mmc_sparse_img()
in the file
  aboot.c
from
  https://us.codeaurora.org/cgit/quic/la/kernel/lk/plain/app/aboot/aboot.c?h=LE.BR.1.2.1Signed-off-by: NSteve Rae <srae@broadcom.com>

This file originally came from upstream code.

While retaining the storage abstraction feature, this is the first
set of the changes required to resync with the
  cmd_flash_mmc_sparse_img()
in the file
  aboot.c
from
  https://us.codeaurora.org/cgit/quic/la/kernel/lk/plain/app/aboot/aboot.c?h=LE.BR.1.2.1Signed-off-by: NSteve Rae <srae@broadcom.com>

This "session-id" alogrithm is not required, and currently corrupts
the stored image whenever more the one "session" is required.
Signed-off-by: NSteve Rae <srae@broadcom.com>

These condition checking are wrong.
Original Author's intention might be "&" instead of "&&".
It can know whether receive or transmit data request with
BIT[4]/BIT[5] of RINTSTS register.
Signed-off-by: NJaehoon Chung <jh80.chung@samsung.com>
Signed-off-by: NMinkyu Kang <mk7.kang@samsung.com>

add DM and DTS support for the at91 based siemens
boards.
Signed-off-by: NHeiko Schocher <hs@denx.de>
Reviewed-by: NAndreas Bießmann <andreas@biessmann.org>
[rebased on current ToT]
Signed-off-by: NAndreas Bießmann <andreas@biessmann.org>

Signed-off-by: NHeiko Schocher <hs@denx.de>
Reviewed-by: NAndreas Bießmann <andreas@biessmann.org>
[rebased on current ToT]
Signed-off-by: NAndreas Bießmann <andreas@biessmann.org>

Add this files from Linux v4.6-rc5

66b8a424d: [workqueue: fix ghost PENDING flag while doing MQ IO]
Signed-off-by: NHeiko Schocher <hs@denx.de>
Acked-by: NAndreas Bießmann <andreas@biessmann.org>

Signed-off-by: NHeiko Schocher <hs@denx.de>
Reviewed-by: NAndreas Bießmann <andreas@biessmann.org>
[rebase on current ToT, don't delete gurnard DTB creation]
Signed-off-by: NAndreas Bießmann <andreas@biessmann.org>

add support for CONFIG_AT91SAM9M10G45.
Signed-off-by: NHeiko Schocher <hs@denx.de>
Reviewed-by: NAndreas Bießmann <andreas@biessmann.org>

Since the spl_boot_mode() is now passed the boot device to boot from,
make use of it instead of inquiring for the boot device again. This
allows board_boot_order() to function correctly.
Signed-off-by: NMarek Vasut <marex@denx.de>
Cc: Andreas Bießmann <andreas.devel@googlemail.com>
Reviewed-by: NAndreas Bießmann <andreas@biessmann.org>

The SPL code already knows which boot device it calls the spl_boot_mode()
on, so pass that information into the function. This allows the code of
spl_boot_mode() avoid invoking spl_boot_device() again, but it also lets
board_boot_order() correctly alter the behavior of the boot process.

The later one is important, since in certain cases, it is desired that
spl_boot_device() return value be overriden using board_boot_order().
Signed-off-by: NMarek Vasut <marex@denx.de>
Cc: Andreas Bießmann <andreas.devel@googlemail.com>
Cc: Albert Aribaud <albert.u.boot@aribaud.net>
Cc: Tom Rini <trini@konsulko.com>
Reviewed-by: NAndreas Bießmann <andreas@biessmann.org>
[add newly introduced zynq variant]
Signed-aff-by: NAndreas Bießmann <andreas@biessmann.org>

If the final targets depend on both "dtbs" and "dts/dt.dtb",
and -j option is given to the command line, multiple threads
descend into the dts/ directory, which causes build error.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: NAndreas Dannenberg <dannenberg@ti.com>

The distro script is supposed to use the internal fdt as fallback if we
find no viable other option. However, we're missing a space key to actually
make that work.

Add the space, so we can successfully load an EFI blob even when there is
no device tree provided on the target device.
Signed-off-by: NAlexander Graf <agraf@suse.de>

Rename B&R kwb board to brxre1
Signed-off-by: NHannes Schmelzer <oe5hpm@oevsv.at>
Reviewed-by: NTom Rini <trini@konsulko.com>

Rename B&R tseries board to brppt1
Signed-off-by: NHannes Schmelzer <oe5hpm@oevsv.at>
Reviewed-by: NTom Rini <trini@konsulko.com>

The handling of the "usage counter" is incorrect, and the clock should
only be disabled when transitioning from 1 to 0.
Reported-by: NChris Brand <chris.brand@broadcom.com>
Signed-off-by: NSteve Rae <srae@broadcom.com>

The Kona Peripheral Slave CCU has 4 policy mask registers, not 8.
Signed-off-by: NChris Brand <chris.brand@broadcom.com>
Signed-off-by: NSteve Rae <srae@broadcom.com>

Choose the Kconfig boot0 hook option and implement the required code.
Signed-off-by: NSteve Rae <srae@broadcom.com>

The Kona PHY supports an 8-bit wide UTMI interface,
therefore, choose this Kconfig setting.
Signed-off-by: NSteve Rae <srae@broadcom.com>

clk->id is unsigned, so it can't be < 0. Remove the check for that.

FWIW, this issue was introduced when the clock API converted e.g.
clk_get_rate()'s clock ID parameter from an int to an unsigned long
(with a struct clk), without removing this check.

Fixes: 135aa950 ("clk: convert API to match reset/mailbox style")
Reported-by: Coverity Scan
Signed-off-by: NStephen Warren <swarren@nvidia.com>
Acked-by: NSimon Glass <sjg@chromium.org>

Signed-off-by: NAndrej Rosano <andrej@inversepath.com>

Use Kbuild standard style where possible.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

There is no more define of CONFIG_SYS_HUSH_PARSER.  Rename some
remaining references and drop the backward compatible Kconfig entry.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

I still see some defines of this config in board headers.  Move them
to defconfigs (+ renaming to CONFIG_HUSH_PARSER) to complete this
migration.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

This empty line should not be there. Remove it.
Signed-off-by: NAndre Renaud <andre@designa-electronics.com>
Reviewed-by: NAndreas Bießmann <andreas@biessmann.org>
Signed-off-by: NSimon Glass <sjg@chromium.org>

Match the #ifdef ... #endif and the code,

   ret = do_something();
   if (ret)
           return ret;

This will make it easier to add more #ifdef'ed code.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

gic_kick_secondary_cpus can directly return to the caller of
smp_kick_all_cpus.  We do not have to use x29 register here.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>
Reviewed-by: NYork Sun <york.sun@nxp.com>

When the input data is not compressed at all,
lzo1x_decompress_safe will fail, so call memcpy()
instead.
Signed-off-by: NJoris Lijssens <joris.lijssens@gmail.com>

If CONFIG_ENV_VARS_UBOOT_CONFIG is enabled (it is by distro), this
code causes build error for boards without CONFIG_SYS_{CPU,_BOARD}.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

Embedding timestamps in FIT images results in unreproducible builds
for targets that generate a fit image, such as dra7xx_evm.

This patch uses the SOURCE_DATE_EPOCH environment variable, when set,
to use specified value for the date.

Thanks to HW42 for debugging the issue and providing the patch:

  https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160606/005722.html

For more information about reproducible builds and the
SOURCE_DATE_EPOCH specification:

  https://reproducible-builds.org/specs/source-date-epoch/
  https://reproducible-builds.org/Signed-off-by: NVagrant Cascadian <vagrant@debian.org>
Reviewed-by: NSimon Glass <sjg@chromium.org>

The output reported may be locale-dependent, which results in
unreproducible builds.

  $ LANG=C ld --version | head -n 1
    GNU ld (GNU Binutils for Debian) 2.26

  $ LANG=it_CH.UTF-8 ld --version | head -n 1
    ld di GNU (GNU Binutils for Debian) 2.26

Forcing LC_ALL=C ensures the output is consistant regardless of the
build environment.

Thanks to HW42 for debugging the issue:

  https://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20160606/005722.html

For more information about reproducible builds:

  https://reproducible-builds.org/Signed-off-by: NVagrant Cascadian <vagrant@debian.org>
Reviewed-by: NTom Rini <trini@konsulko.com>

s/hardkernel/amlogic/ to have a single place for all the amlogic-based
boards.
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NCarlo Caione <carlo@endlessm.com>
Acked-by: NBeniamino Galvani <b.galvani@gmail.com>

Introduce a meson-gxbb-common.h header file and derive the
configuration for Hardkernel Odroid-C2 board from that.
Reviewed-by: NSimon Glass <sjg@chromium.org>
Signed-off-by: NCarlo Caione <carlo@endlessm.com>
Acked-by: NBeniamino Galvani <b.galvani@gmail.com>

We already support iminfo for other images. The idea
of this patch is start to have a minimal support for
android image format. We still need to print id[] array
Signed-off-by: NMichael Trimarchi <michael@amarulasolutions.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

When building a FIT with external data (-E), U-Boot proper may require
absolute positioning for executing the external firmware. To acheive this
use the (-p) switch, which will replace the amended 'data-offset' with
'data-position' indicating the absolute position of external data.

It is considered an error if the requested absolute position overlaps with the
initial data required for the compact FIT.
Signed-off-by: NTeddy Reed <teddy.reed@gmail.com>

Short help (description) in bootefi command has a trailing "\n" that
breaks the "help" command output (empty line after "bootefi").

Nothing important, doesn't affect anything but better be fixed in the
upcoming release.

Still working on i.MX6 and their siblings NAND U-Boot update -- it
works here but not ready for a submission yet. Anyway it is for the
next cycle, not going to go into this release because it is too big
and may affect something else.

Also have some thoughts about fastboot (using multiple devices) but
this will go into separate email with RFC.
Signed-off-by: NSergey Kubushyn <ksi@koi8.net>