bcm63xx/u-boot/board/sandbox, branch master

Merge tag 'pull-24apr19' of git://git.denx.de/u-boot-dm

2019-04-24T16:27:29Z

Various minor sandbox iumprovements Fixes for tracing with sandbox Refactoring for boot_get_fdt()

sandbox: Move pre-console buffer out of the way of tracing

2019-04-24T02:26:43Z

These two buffers currently conflict if tracing is enabled. Move the pre-console buffer and update the documentation. Signed-off-by: Simon Glass

sandbox: Improve debugging in initcall_run_list()

2019-04-24T02:26:43Z

At present if one of the initcalls fails on sandbox the address printing is not help, e.g.: initcall sequence 0000557678967c80 failed at call 00005576709dfe1f (err=-96) This is because U-Boot gets relocated high into memory and the relocation offset (gd->reloc_off) does not work correctly for sandbox. Add support for finding the base address of the text region (at least on Linux) and use that to set the relocation offset. This makes the output better: initcall sequence 0000560775957c80 failed at call 0000000000048134 (err=-96) Then you use can use grep to see which init call failed, e.g.: $ grep 0000000000048134 u-boot.map stdio_add_devices Of course another option is to run it with a debugger such as gdb: $ gdb u-boot ... (gdb) br initcall.h:41 Breakpoint 1 at 0x4db9d: initcall.h:41. (2 locations) Note that two locations are reported, since this function is used in both board_init_f() and board_init_r(). (gdb) r Starting program: /tmp/b/sandbox/u-boot [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". U-Boot 2018.09-00264-ge0c2ba9814-dirty (Sep 22 2018 - 12:21:46 -0600) DRAM: 128 MiB MMC: Breakpoint 1, initcall_run_list (init_sequence=0x5555559619e0 ) at /scratch/sglass/cosarm/src/third_party/u-boot/files/include/initcall.h:41 41 printf("initcall sequence %p failed at call %p (err=%d)\n", (gdb) print *init_fnc_ptr $1 = (const init_fnc_t) 0x55555559c114 (gdb) Signed-off-by: Simon Glass

regmap: fix regmap_read_poll_timeout warning about sandbox_timer_add_offset

2019-04-23T09:17:15Z

When fixing sandbox test for regmap_read_poll_timeout(), the sandbox_timer_add_offset was introduced but only defined in sandbox code thus generating warnings when used out of sandbox : include/regmap.h:289:2: note: in expansion of macro 'regmap_read_poll_timeout_test' regmap_read_poll_timeout_test(map, addr, val, cond, sleep_us, \ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ drivers/spi/meson_spifc.c:169:8: note: in expansion of macro 'regmap_read_poll_timeout' ret = regmap_read_poll_timeout(spifc->regmap, REG_SLAVE, data, ^~~~~~~~~~~~~~~~~~~~~~~~ drivers/spi/meson_spifc.c: In function 'meson_spifc_txrx': include/regmap.h:277:4: warning: implicit declaration of function 'sandbox_timer_add_offset' [-Wimplicit-function-declaration] This fix adds a timer_test_add_offset() only defined in sandbox, and renames the previous sandbox_timer_add_offset() to it. Cc: Simon Glass Reported-by: Tom Rini Fixes: df9cf1cc08 ("test: dm: regmap: Fix the long test delay") Signed-off-by: Neil Armstrong Reviewed-by: Simon Glass

sandbox: Add a memory map to the sandbox README

2018-11-26T13:25:35Z

We have a few things in the memory map now, so add documentation for this to avoid confusion. Also note that it is possible to run all tests now. Signed-off-by: Simon Glass

sandbox: cros_ec: exynos: Drop use of cros_ec_get_error()

2018-11-21T02:14:22Z

This function is really just a call to uclass_get_device() and there is no reason why the caller cannot do it. Update sandbox and snow accordingly. Signed-off-by: Simon Glass Acked-by: Minkyu Kang

sandbox: README: use setenv ethrotate no

2018-11-21T02:14:22Z

If we want to control which network interface is actually used, we have to issue 'setenv ethrotate no'. If ethrotate is not set any interface may be used. Signed-off-by: Heinrich Schuchardt Reviewed-by: Simon Glass

sandbox: README: setting environment variables

2018-11-21T02:14:22Z

The command to set environment variables is setenv. Signed-off-by: Heinrich Schuchardt Reviewed-by: Simon Glass

sandbox: Add an explanation of the sandbox variants

2018-09-29T17:49:35Z

There are quite a few builds of sandbox now. Add information about these to the README. Signed-off-by: Simon Glass

sandbox: led: use new function to configure default state

2018-08-10T14:27:32Z

Initialize the led with the default state defined in device tree in board_init and solve issue with test for led default state. Reviewed-by: Simon Glass Signed-off-by: Patrick Delaunay