Currently, USB is forced-enabled for the sunxi familly, and there is no
way to disable it.

However, USB takes a long time to initiliase, delaying the boot by up to
5 seconds (without any USB device attached!). This is a very long delay,
especially in cases where USB booting is not wanted at all, and where
the device is expected to boot relatively often (even in production).

Change the way the dependencies are handled, by only forcibly selecting
USB when CONFIG_DISTRO_DEFAULTS ("defaults suitable for booting general
purpose Linux distributions") is set. This option defaults to y for the
sunxi familly, so the current default behaviour is kept unchanged. Users
interested in boot time and/or size will be able to disable this to
further disable USB.

With USB disabled, the time spent in U-Boot before handing control to
the Linux kernel is about 1s now, down from ~5s (Nanopi Neo, sunxi H3).
Signed-off-by: N"Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Ian Campbell <ijc@hellion.org.uk>
Cc: Hans De Goede <hdegoede@redhat.com>
Reviewed-by: NHans de Goede <hdegoede@redhat.com>
Signed-off-by: NHans de Goede <hdegoede@redhat.com>

Use the already available Kconfig option for AHCI. Tested on the
BananaPi.
Signed-off-by: NJelle van der Waa <jelle@vdwaa.nl>
Reviewed-by: NHans de Goede <hdegoede@redhat.com>
Signed-off-by: NHans de Goede <hdegoede@redhat.com>

We have all the building blocks now to run arbitrary efi applications
in travis. The most important one out there is grub2, so let's add
a simple test to verify that grub2 still comes up.
Signed-off-by: NAlexander Graf <agraf@suse.de>

Most of the time when running the sleep test in Travis for
the integratorcp_cm926ejs target I get errors like this:

  E       assert 2.999901056289673 >= 3

The deviation is tiny, but fails the overall build result. Since
the sleep test is not terribly important as gate keeper for travis
tests, let's just exclude it for this board.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Reviewed-by: NTom Rini <trini@konsulko.com>

Today we can compile a self-contained hello world efi test binary that
allows us to quickly verify whether the EFI loader framwork works.

We can use that binary outside of the self-contained test case though,
by providing it to a to-be-tested system via tftp.

This patch separates compilation of the helloworld.efi file from
including it in the u-boot binary for "bootefi hello". It also modifies
the efi_loader test case to enable travis to pick up the compiled file.
Because we're now no longer bloating the resulting u-boot binary, we
can enable compilation always, giving us good travis test coverage.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Reviewed-by: NTom Rini <trini@konsulko.com>

Now that we have working network tests and a hello world efi application
built inside our tree, we can automatically test that efi binary running
inside of U-Boot.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NTom Rini <trini@konsulko.com>

When running in travis-ci, we want to pass environment configuration to
the tests. These reside in a path available through PYTHONPATH, so let's
define that one to point to the unit test repo.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Reviewed-by: NTom Rini <trini@konsulko.com>

Some travis QEMU tests can transfer files between the build directory
and the guest U-Boot instance. For that to work, both need to have access
to the same directory.

This patch puts the current build path into an environment variable, so
that the environment generating python scripts can extract it from there
and read the respective files.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Reviewed-by: NTom Rini <trini@konsulko.com>

The network test currently downloads files at 0MB offset of RAM start.
This works for most ARM systems, but x86 has weird memory layout constraints
on the first MB of RAM.

To not get caught into any of these, let's add a 4MB pad from start
of RAM to the default memory offset.
Signed-off-by: NAlexander Graf <agraf@suse.de>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NTom Rini <trini@konsulko.com>

It should be 112M, to make rootfs start at 0x40000
Signed-off-by: NJacob Chen <jacob2.chen@rock-chips.com>
Acked-by: NSimon Glass <sjg@chromium.org>

This adds support for the Asus Chromebook Flip, an RK3288-based clamshell
device which can flip into 'tablet' mode. The device tree file comes from
Linux v4.8. The SDRAM parameters are for 4GB Samsung LPDDR3.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This adds support for the Asus Chromebit, and RK3288-based device designed
to plug directly into an HDMI monitor. The device tree file comes from
Linux v4.8.
Signed-off-by: NSimon Glass <sjg@chromium.org>

It makes not sense using u8 to hold a value on a 32-bit or 64-bit machine.
It can only bloat the code by forcing the compiler to mask the value.
Change it to uint.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Update board_init() to increase the ARM clock to the maximum speed on
veyron boards. This makes quite a large difference in performance. With
this change, speed goes from about 750 DMIPS to 2720 DMIPs.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Add basic support for setting the ARM clock, since this allows us to run
at maximum speed in U-Boot. Currently only a single speed is supported
(1.8GHz).
Signed-off-by: NSimon Glass <sjg@chromium.org>

The SDRAM settings are not common across all veyron models. Move the
current settings into Jerry's file.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Add a comment to indicate that we are not supporting the PWM regulator
yet.
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present we have a single rk3288-based Chromebook: chromebook_jerry. But
all such Chromebooks can use the same binary with only device-tree
differences. The family name is 'veyron', so rename the files accordingly.

Also update the device-tree filename since this currently differs from
Linux.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Adjust jerry to use of-platdata like other rk3288 boards. This reduces the
SPL size enough that it boots again.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Check whether a display device is in use before using it. Add a comment as
to why two displays cannot currently be used at the same time.

This allows us to remove the device-tree change that disables vopb on
jerry.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Mark a display as in use when display_enable() is called. This can avoid
a display being used by multiple video-output devices.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Sometimes the frame buffer is not a multiple of the cache line size.
Adjust the cache-flushing code to avoid cache warnings/errors in this
case.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This is an uncommon error but we may as well have a debug() message when
it happens.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This is not currently implemented. Add support for this so that the Chrome
OS EC can be used on jerry.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Allow this driver to be used with of-platdata on rk3288.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Some boards may want to use these subsystems with of-platdata in SPL. Add
support for this by avoiding any device tree access in this case.
Signed-off-by: NSimon Glass <sjg@chromium.org>

The current code assumes that the devices are ordered corresponding to
their alias value. But (for example) video1 can come before video0 in the
device tree.

Correct this, by always looking for device 0 first. After that we can fall
back to finding the first available device.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Fix a few code style nits in stdio_get_by_name().
Signed-off-by: NSimon Glass <sjg@chromium.org>

This board always boots from SPI, so update the code to support that with
of-platdata. The boot source is not currently available with of-platdata.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This code incorrectly uses the oscillator. It should use the clock
selected in the device tree.
Signed-off-by: NSimon Glass <sjg@chromium.org>
Fixes: 135aa950 (clk: convert API to match reset/mailbox style)

This code currently always selects the second source. It only worked
because both sources are set up.

With the change to only init video devices that are present in the stdout
environment variable, this fails. Fix it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

add fix regulator node for usb vbus power control.
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
Acked-by: NSimon Glass <sjg@chromium.org>

usb host vbus power is using gpio fix regulator, enable it.
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
Acked-by: NSimon Glass <sjg@chromium.org>

rk3036 using dwc2 usb controller, need enable relate configs for it.
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
Acked-by: NSimon Glass <sjg@chromium.org>

PWM_ROCKCHIP need to enable for PWM regulator, this config
is missing during rebase and new patch set in previous submission.
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
Acked-by: NSimon Glass <sjg@chromium.org>

The size dram node need to be deduced by the same amount of reserved space.
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
Acked-by: NSimon Glass <sjg@chromium.org>

UART,s -> UARTs, to avoid this spreading via copy&paste.
Signed-off-by: NAndreas Färber <afaerber@suse.de>
Acked-by: NSimon Glass <sjg@chromium.org>

Sort rk3036 before rk3288.
Signed-off-by: NAndreas Färber <afaerber@suse.de>
Acked-by: NSimon Glass <sjg@chromium.org>

Currently the specific set ops functions are directly
called without any check for min/max current limits for a regulator.
Check for them and proceed.
Signed-off-by: NKeerthy <j-keerthy@ti.com>
Fixed checking of current limits:
Signed-off-by: NSimon Glass <sjg@chromium.org>