doc/README.log was already moved to doc/develop/logging.rst but has been
recreated by an incorrect merge.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Since the previous patch, net_init now exposes some errors, so check for
them.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

net_init does not always succeed, and there is no existing mechanism to
discover errors. This patch allows callers of net_init (such as net_init)
to handle errors. The root issue is that eth_get_dev can fail, but
net_init_loop doesn't expose that. The ideal way to fix eth_get_dev would
be to return an error with ERR_PTR, but there are a lot of callers, and all
of them just check if it's NULL. Another approach would be to change the
signature to something like

int eth_get_dev(struct udevice **pdev)

but that would require rewriting all of the many callers.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

This driver interferes with other sandbox tests since it causes log output
to be interspersed with "No ethernet found." messages. Disable this driver
by default.

Enable it for the syslog tests so that they still pass.
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present all log devices are enabled by default. Add a function to allow
devices to be disabled or enabled at runtime.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This is not needed as the Makefile only builds the file if CONFIG_LOG_TEST
is enabled. Drop it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present there is no way to disable a log driver. But the syslog driver
causes (attempted) network traffic in sandbox every time a log message
is printed, which is often.

Add a flag to enable a log driver. Adjust struct log_device to use a short
for next_filter_num so that no more memory is used for devices. Also fix
a missing line in the struct log_driver comment while here.

To maintain compatibility, enable it for all drivers for now.
Signed-off-by: NSimon Glass <sjg@chromium.org>

It is sometimes useful to output hex dumps in SPL. Add a config option to
allow this.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NStefan Roese <sr@denx.de>

At present if CONFIG_LOG enabled, putting LOG_DEBUG at the top of a file
(before log.h inclusion) causes _log() to be executed for every log()
call, regardless of the build- or run-time logging level.

However there is no guarantee that the log record will actually be
displayed. If the current log level is lower than LOGL_DEBUG then it will
not be.

Add a way to signal that the log record should always be displayed and
update log_passes_filters() to handle this.

With the new behaviour, log_debug() will always log if LOG_DEBUG is
enabled.

Move log_test_syslog_nodebug() into its own file since it cannot be made
to work where it is, with LOG_DEBUG defined.
Signed-off-by: NSimon Glass <sjg@chromium.org>

- Re-organize a number of Kconfig related entries to be better organized
  for long term maintenance.

Rsync all defconfig files using moveconfig.py
Signed-off-by: NTom Rini <trini@konsulko.com>

At present MKIMAGE_DTC_PATH is in the devicetree menu but not within
'devicetree control' since it does not relate to that. As a result it
shows up in the top menu.

It actually relates to the mkimage tool, so create a new tools menu for it
and move it there.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This actually relates to something displayed on start-up, so move it into
that menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This option does not belong at the top level. Move it under generic
driver options.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This relates to the environment so should not be at the top level. Move
it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

These are start-up hooks so put them under that menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

These hooks relate to U-Boot init so move them under that menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

There are quite a few options at the top level relating to U-Boot init.
Move them into their own menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This relates to booting since it is the default devicetree provided to
Linux. Move it under the 'boot options' menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This relates to booting, so move it under the 'boot images' menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

There are a number of miscellaneous boot images at the top level of the
kconfig menu. Move these into the 'boot options' menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This option relates to autoboot, so move it there.
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present the autoboot options are in cmd/Kconfig but they don't really
relate to commands. They relate to booting, so move this menu under the
boot menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This relates to booting, so move it under the boot menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This relates to booting, so move it under the boot menu.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Most of the boot options are in common/Kconfig but that file is already
extremely large. Create a new Kconfig.boot to hold the boot options.
Signed-off-by: NSimon Glass <sjg@chromium.org>

There are quite a few boot-related menu options at the top level. Create a
new menu to hold these and move 'Boot images' into it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

- Move ASPEED ram driver, update.
- Exhance pinctrl/gpio support, update Kendryte K210 support
- Enhance qemu_arm64 support for a single binary to work with and
  without TF-A

Now that PIE works when U-Boot is started from ROM, let's enable
CONFIG_POSITION_INDEPENDENT, which allows to load U-Boot also via
ARM Trusted-Firmware's fip.bin to DRAM, without tweaking the
configuration.

To get a writable initial stack, we need to keep the fixed initial
stack pointer, which points to DRAM in our case.
Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
Reviewed-by: NStephen Warren <swarren@nvidia.com>

CONFIG_ARCH_SUPPORT_TFABOOT was used on the qemu-arm64 platform to
guard a tweak to the flash bank configuration. U-Boot now reads the
current flash setup from the devicetree, so there is no need for
this option anymore.
Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

Currently we hard-code the number and initial addresses of QEMU's flash
banks, even though our code is perfectly able to gather the same
information from the DTB provided by QEMU.
This is especially annoying, since we have two slightly different
U-Boot configurations ("bare-metal" vs. loaded via Arm Trusted
Firmware), which need to be selected at build time.

Drop the two hard coded alternatives, and use
CONFIG_SYS_MAX_FLASH_BANKS_DETECT instead, which relies on the DTB to
figure out the actual flash configuration at runtime.
Signed-off-by: NAndre Przywara <andre.przywara@arm.com>

Currently selecting CONFIG_POSITION_INDEPENDENT also forces us to use an
initial stack pointer relative to the beginning of the BSS section.
This makes some sense, because this should be writable memory anyway.

However the BSS section is not cleared or used until later in the
setup process (after relocation), so memory nearby might not be
available early enough to host the initial stack. This is an issue if
U-Boot is loaded from (Flash-)ROM, for instance.

Allow CONFIG_INIT_SP_RELATIVE to be turned off by a board's config, to
be able to select a fixed stack pointer, for instance in known good
DRAM.

This will help QEMU utilising PIE, when it's loaded to (Flash-)ROM.
Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
Reviewed-by: NStephen Warren <swarren@nvidia.com>

When the actual offset between link and runtime address is zero, there
is no need for patching up U-Boot early when running with
CONFIG_POSITION_INDEPENDENT.

Skip the whole routine when the distance is 0.

This helps when U-Boot is loaded into ROM, or in otherwise sensitive
memory locations.
Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
Reviewed-by: NStephen Warren <swarren@nvidia.com>

When we build an arm64 target and enable POSITION_INDEPENDENT, we were
skipping our build-time dynamic relocation fixup routine (STATIC_RELA).

This was probably done because we didn't need it in this case, as the
PIE fixup routine in start.S would take care of that at runtime.

However when we now skip this routine (upon detecting that the fixup
offset is 0), this might lead to uninitialised pointers.

Remove the exception, so that we always do the build-time relocation.

NOTE: GNU binutils starting with v2.27.1 do this build-time relocation
automatically, to be in-line with other architecures. So on newer
toolchains our manual fixup is actually not needed. It doesn't hurt to
have it, though, so that we keep compatibility with the popular Linaro
toolchains, which lack this feature.
Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
Reviewed-by: NStephen Warren <swarren@nvidia.com>

The CONFIG_TFABOOT option is more about what U-Boot DOES NOT need to do
than to support some features.

Explain a bit more in the Kconfig help text to avoid misunderstandings.
Signed-off-by: NAndre Przywara <andre.przywara@arm.com>
Reviewed-by: NTom Rini <trini@konsulko.com>

Most users don't need the standalone API examples. Distributions like SUSE
do not supply libgcc for cross-compiling and we cannot do without on ARMv8
for building examples/.

Make examples selectable via symbol CONFIG_EXAMPLES. It defaults to
yes on ARCH_QEMU to ensure that we compile the API as part of our
continuous integration.

Cc: Matthias Brugger <mbrugger@suse.com>
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: NTom Rini <trini@konsulko.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NMatthias Brugger <mbrugger@suse.com>

The timeout calculation is based on the clk being in KHz but
the clk api returns the clk value in Hz. Convert this to KHz
to calculate the correct timeout value.
Signed-off-by: NJack Mitchell <ml@embed.me.uk>

This patch adds the necessary configs and docs for FPIOA and GPIO support
on the K210.
Signed-off-by: NSean Anderson <seanga2@gmail.com>

Add a device tree binding for the BOOT button on the Maix board.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: NSean Anderson <seanga2@gmail.com>
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NRick Chen <rick@andestech.com>

This patch adds the necessary device tree bindings.
Signed-off-by: NSean Anderson <seanga2@gmail.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Acked-by: NRick Chen <rick@andestech.com>