There is a spelling mistake and two functions are missing comments
altogether. Also the flags declaration is correct, but doesn't follow
style. Finally, the uclass_get_device() function has some errors in
its documentation.

Fix these problems.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NMarek Vasut <marex@denx.de>

Enable driver model for Tegra boards.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NStephen Warren <swarren@nvidia.com>

These files are taken from Linux 3.14.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NStephen Warren <swarren@nvidia.com>

The values here are int, but the map_to_sysmem() call can return a long.
Add a cast to deal with this.
Signed-off-by: NSimon Glass <sjg@chromium.org>

The GPIO tests require the sandbox GPIO driver, so cannot be run on other
platforms. Similarly for the 'dm test' command.
Signed-off-by: NSimon Glass <sjg@chromium.org>

In a very few cases we need to adjust the driver model root device, such as
when setting it up at initialisation. Add a macro to make this easier.
Signed-off-by: NSimon Glass <sjg@chromium.org>

These files don't compile in some architectures. Fix it by adding the
missing headers.
Signed-off-by: NSimon Glass <sjg@chromium.org>

We want 'N0' and 'n0' to mean the same thing, so ensure that case is not
considered when naming GPIO banks.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Add a note to encourage people to convert drivers to use driver model.
Signed-off-by: NSimon Glass <sjg@chromium.org>

It is best to avoid having any occurence of 'struct device' in driver
model, so rename to achieve this.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Linux supports this, and if we are to have compatible device tree files,
U-Boot should also.

Avoid giving the device tree files access to U-Boot's include/ directory.
Only include/dt-bindings is accessible.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NStephen Warren <swarren@nvidia.com>
Reviewed-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>

Support the iotrace feature for sandbox, and enable it, using some dummy
I/O access methods.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Support the iotrace feature for ARM, when enabled.
Signed-off-by: NSimon Glass <sjg@chromium.org>

When debugging drivers it is useful to see what I/O accesses were done
and in what order.

Even if the individual accesses are of little interest it can be useful to
verify that the access pattern is consistent each time an operation is
performed. In this case a checksum can be used to characterise the operation
of a driver. The checksum can be compared across different runs of the
operation to verify that the driver is working properly.

In particular, when performing major refactoring of the driver, where the
access pattern should not change, the checksum provides assurance that the
refactoring work has not broken the driver.

Add an I/O tracing feature and associated commands to provide this facility.
It works by sneaking into the io.h heder for an architecture and redirecting
I/O accesses through its tracing mechanism.

For now no commands are provided to examine the trace buffer. The format is
fairly simple, so 'md' is a reasonable substitute.

Note: The checksum feature is only useful for I/O regions where the contents
do not change outside of software control. Where this is not suitable you can
fall back to manually comparing the addresses. It might be useful to enhance
tracing to only checksum the accesses and not the data read/written.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>

commit ecd72950 "Add parameter to md5sum to save the md5 sum"
adds support to build a string to be saved in the env and tries
to zero end it with str_ptr = '\0'; This does actually set the
pointer to the end of the buffer itself to zero. Since the
string was already zero terminated by the sprintf before it,
just remove the line, preventing a clang warning.

cc: Joe Hershberger <joe.hershberger@ni.com>
Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>

nios-32 arch was removed back in 2010 (1117cbf2). Code depending on
its headers (nios.h, nios-io.h) can't possibly compile since then.
As it wasn't fixed till now it is safe to remove.
Signed-off-by: NVasili Galka <vvv444@gmail.com>

This flag does not compile on m68k since 2003 (8bde7f77) when a
required "cmd_bedbug.h" header was removed. Eleven years passed,
lets clean up a little...
Signed-off-by: NVasili Galka <vvv444@gmail.com>

The function tps65090_init checks the i2c bus of p->bus. However
the pointer p is not intialiased at this point. Check the local
variable bus instead.

cc: Tom Wai-Hong Tam <waihong@chromium.org>
Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>
Acked-by: NSimon Glass <sjg@chromium.org>

SPL stage does not support various networking things, and therefore
CONFIG_NETCONSOLE cannot be built within SPL.
Signed-off-by: NHannes Petermaier <oe5hpm@oevsv.at>

commit 18b06652 "tools: include u-boot version of sha256.h"
unconditionally forced the sha256.h from u-boot to be used
for tools instead of the host version. This is fragile though
as it will also include the host version. Therefore move it
to include/u-boot to join u-boot/md5.h etc which were renamed
for the same reason.

cc: Simon Glass <sjg@chromium.org>
Signed-off-by: NJeroen Hofstee <jeroen@myspectrum.nl>

vboot_test.sh uses Bashisms. Explicitly use #!/bin/bash so the script
doesn't fail if /bin/sh isn't Bash.
Signed-off-by: NStephen Warren <swarren@nvidia.com>
Acked-by: NSimon Glass <sjg@chromium.org>

As an example of an end-to-end process for using verified boot in U-Boot,
add a detailed description of the steps to be used for a Beaglebone
Black.
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present this tool only checks the configuration signing. Have it also
look at each of the images in the configuration and confirm that they
verify.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: Heiko Schocher <hs@denx.de> (v1)

This makes it possible to decompress an image without it being a kernel
and without intending to boot it (as it needed for host tools, for example).
Signed-off-by: NSimon Glass <sjg@chromium.org>

We want to use some of the functionality in this file, so make it
build on the host.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This is not necessary and prevents using this header when building tools.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This typo makes the comment confusing. Fix it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

A small change allows this to operate on sandbox.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This can be obtained by looking up the image type, so is redundant. It is
better to centralise this lookup to avoid errors.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This file has code in three different categories:
- Command processing
- OS-specific boot code
- Locating images and setting up to boot

Only the first category really belongs in a file called cmd_bootm.c.

Leave the command processing code where it is. Split out the OS-specific
boot code into bootm_os.c. Split out the other code into bootm.c

Header files and extern declarations are tidied but otherwise no code
changes are made, to make it easier to review.
Signed-off-by: NSimon Glass <sjg@chromium.org>

It is more common to have 0 mean OK, and -ve mean error. Change this
function to work the same way to avoid confusion.
Signed-off-by: NSimon Glass <sjg@chromium.org>

These tools crash if no arguments are provided. Add checks to avoid this.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NHeiko Schocher <hs@denx.de>

This seems like a better name. This is a patch-up to the earlier commit
63b4b5ba, and also removes a redundant Makefile change.
Signed-off-by: NSimon Glass <sjg@chromium.org>

The original code did not cover every case and there was a missing negative
sign in one case. Expand the coverage and fix the bug.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This type is more readily available on the host compiler, so use it instead.
Signed-off-by: NSimon Glass <sjg@chromium.org>

We don't make use of the device tree otherwise yet (and will need to
think how to not break the current multi-board support) and this causes
further breakage with additional changes.
Signed-off-by: NTom Rini <trini@ti.com>

Commit 7d89982b stopped creating symbolic link
arch/${arch}/include/asm/proc.

arch/.gitignore should be updated.
Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
Cc: Vasili Galka <vvv444@gmail.com>

ext4fs_allocate_blocks() always allocates at least one block for a file.
If the file size is zero, this causes total_remaining_blocks to
underflow, which then causes an apparent hang while 2^32 blocks are
allocated.

To solve this, check that total_remaining_blocks is non-zero as part of
the loop condition (i.e. before each loop) rather than at the end of
the loop.
Signed-off-by: NStephen Warren <swarren@nvidia.com>

Before this commit, fdt_initrd() just returned if initrd
start address is zero.
But it is possible if the RAM is located at address 0.

This commit makes the return condition more reasonable:
Just return if the size of initrd is zero.
Signed-off-by: NMasahiro Yamada <yamada.m@jp.panasonic.com>
Acked-by: NSimon Glass <sjg@chromium.org>