This function doesn't need to be exported, and with verification
we want to use it for setting the 'value' property in any node,
so rename it.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NMarek Vasut <marex@denx.de>

This function has become quite long and much of the body is indented quite
a bit. Move it into a separate function to make it easier to work with.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NMarek Vasut <marex@denx.de>

This code is never compiled into U-Boot, so move it into a separate
file in tools/ to avoid the large #ifdef.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NMarek Vasut <marex@denx.de>

The FIT code is about half the size of the >3000-line image.c. Split this
code into its own file.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NMarek Vasut <marex@denx.de>

One we split out the FIT code from image.c we will need this function.
Export it in the header.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NMarek Vasut <marex@denx.de>

Rather than repeat the line
 #if defined(CONFIG_TIMESTAMP) || defined(CONFIG_CMD_DATE) || \
	defined(USE_HOSTCC)

everywhere, put this in a header file and #define IMAGE_ENABLE_TIMESTAMP
to either 1 or 0. Then we can use a plain if() in most code and avoid
the #ifdefs.

The compiler's dead code elimination ensures that the result is the same.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NMarek Vasut <marex@denx.de>

Iterating through subnodes with libfdt is a little painful to write as we
need something like this:

for (depth = 0, count = 0,
	offset = fdt_next_node(fdt, parent_offset, &depth);
     (offset >= 0) && (depth > 0);
     offset = fdt_next_node(fdt, offset, &depth)) {
	if (depth == 1) {
		/* code body */
	}
}

Using fdt_next_subnode() we can instead write this, which is shorter and
easier to get right:

for (offset = fdt_first_subnode(fdt, parent_offset);
     offset >= 0;
     offset = fdt_next_subnode(fdt, offset)) {
	/* code body */
}

Also, it doesn't require two levels of indentation for the loop body.
Signed-off-by: NSimon Glass <sjg@chromium.org>
(Cherry-picked from dtc commit 4e76ec79)
Acked-by: NGerald Van Baren <vanbaren@cideas.com>

Move this definition from aisimage.c to mkimage.h so that it is available
more widely.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NMarek Vasut <marex@denx.de>

We don't measure boot timing on the host, or with SPL, so use both
conditions in the bootstage header. This allows us to avoid using
conditional compilation around bootstage_...() calls. (#ifdef)
Signed-off-by: NSimon Glass <sjg@chromium.org>

Rather than needing to call one of many hashing algorithms in U-Boot,
provide a function hash_block() which handles this, and can support all
available hash algorithms.

Once we have md5 supported within hashing, we can use this function in
the FIT image code.
Signed-off-by: NSimon Glass <sjg@chromium.org>

A few things have changed since this doc was written, so update it to
match the current state of things.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This should say 'environmnent'.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Add selected coreboot timestamps into bootstage to get a unified view of
the boot timings.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Coreboot provides a lot of useful timing information. Provide a facility
to add this to bootstage on start-up.
Signed-off-by: NSimon Glass <sjg@chromium.org>

We don't use zlib and gzip but do use lzo, so enable this.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This local variable is not used unless CONFIG_GZIP is defined. Fix it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Add a function which allows a (file, function, line number) to be marked
in bootstage.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NChe-Liang Chiou <clchiou@chromium.org>

This is a convenient way of finding out where boottime is going. Enable
it for coreboot.
Signed-off-by: NSimon Glass <sjg@chromium.org>

In a previous CL we added the bootstage_relocate(), which should be
called after malloc is initted.  Now we call it on generic board.
Signed-off-by: NDoug Anderson <dianders@chromium.org>
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Any pointers to name strings that were passed to bootstage_mark_name()
pre-relocation should be copied post-relocation so that they don't get
trashed as the original location of U-Boot is re-used for other
purposes.

This change introduces a new API call that should be called from
board_init_r() after malloc has been initted on any board that uses
bootstage.
Signed-off-by: NDoug Anderson <dianders@chromium.org>
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Some functions don't have a stub for when CONFIG_BOOTSTAGE is not defined.
Add one to avoid #ifdefs in the code when this is used in U-Boot.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NChe-Liang Chiou <clchiou@chromium.org>
Reviewed-by: NTom Wai-Hong Tam <waihong@chromium.org>

While we don't want PCAT timers for timing, we want timer 2 so that we can
still make a beep. Re-purpose the PCAT driver for this, and enable it in
coreboot.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This is no longer used since we prefer the more accurate TSC timer, so
remove the dead code.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NGraeme Russ <graeme.russ@gmail.com>

Tidy up some old broken and unneeded implementations. These are not used
by coreboot or anything else now.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NGabe Black <gabeblack@chromium.org>
Reviewed-by: NMichael Spang <spang@chromium.org>
Reviewed-by: NVadim Bendebury <vbendeb@chromium.org>
Acked-by: NGraeme Russ <graeme.russ@gmail.com>

This timer runs at a rate that can be calculated, well over 100MHz. It is
ideal for accurate timing and does not need interrupt servicing.

Tidy up some old broken and unneeded implementations at the same time.

To provide a consistent view of boot time, we use the same time
base as coreboot. Use the base timestamp supplied by coreboot
as U-Boot's base time.

Signed-off-by: Simon Glass <sjg@chromium.org>base
Signed-off-by: NSimon Glass <sjg@chromium.org>

The 'Starting linux' message appears twice in the code, but both call
through the same place. Unify these and add calls to bootstage to
mark the occasion.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NMichael Spang <spang@chromium.org>
Acked-by: NGraeme Russ <graeme.russ@gmail.com>

panic_puts() can be called in early boot to display a message. It might
help with early debugging.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NTom Wai-Hong Tam <waihong@chromium.org>

Several files use the global_data pointer without declaring it. This works
because the declaration is currently a NOP. But still it is better to
fix this so that x86 lines up with other archs.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Since we use CONFIG_SYS_GENERIC_BOARD on x86, we don't need this anymore.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NGraeme Russ <graeme.russ@gmail.com>

Since we don't have real-mode code now, we can remove this chunk of the link
script.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NGraeme Russ <graeme.russ@gmail.com>

Graeme Russ pointed out that this code is no longer used. Remove it.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Acked-by: NGraeme Russ <graeme.russ@gmail.com>

Commit 18652864 (Introduce generic link
section.h symbol files) changed the __bss_end symbol type from char[] to
ulong. This led to wrong relocation parameters which ended up in a not working
u-boot. Unfortunately this is not clear to see cause due to RAM aliasing we
may get a 'half-working' u-boot then.

Fix this by dereferencing the __bss_end symbol where needed.
Signed-off-by: NAndreas Bießmann <andreas.devel@googlemail.com>

The gpio spec for bf54x and bf60x differ a lot from the old gpio driver for bf5xx.
A lot of machine macros are used to accomodate both code in one gpio driver.
This patch split the old gpio driver and move new gpio2 support to the generic
gpio driver folder.

- To enable gpio2 driver, macro CONFIG_ADI_GPIO2 should be defined in the board's
config header file.
- The gpio2 driver supports bf54x, bf60x and future ADI processors, while the
older gpio driver supports bf50x, bf51x, bf52x, bf53x and bf561.
- All blackfin specific gpio function names are replaced by the generic gpio APIs.
Signed-off-by: NSonic Zhang <sonic.zhang@analog.com>

Signed-off-by: NMarek Vasut <marex@denx.de>
Signed-off-by: NSonic Zhang <sonic.zhang@analog.com>

- Add comments for watchdog event initialization.
- Make sure the writting operation to MMRs are finished.
Signed-off-by: NSonic Zhang <sonic.zhang@analog.com>

- Move blackfin serial driver to the generic driver folder.
- Move blackfin serial headers to blackfin arch head folder.
- Update the include path to blackfin serial header in start up code.
Signed-off-by: NSonic Zhang <sonic.zhang@analog.com>

- Enable hw_watchdog_init() in watchdog.h if CONFIG_HW_WATCHDOG is defined.
- Move blackfin hw watchdog driver to the generic driver folder.
- Call hw_watchdog_init() from blackfin board init code.
- Reuse macro CONFIG_WATCHDOG_TIMEOUT_MSECS
- Update README.watchdog accordingly
Signed-off-by: NSonic Zhang <sonic.zhang@analog.com>

- BF609 spi driver depend on this.
Signed-off-by: NScott Jiang <scott.jiang.linux@gmail.com>
Signed-off-by: NSonic Zhang <sonic.zhang@analog.com>