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>

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

Signed-off-by: NTom Rini <trini@konsulko.com>

Conflicts:
	arch/arm/Kconfig

In case we want to force a particular value on a regulator
irrespective of the min/max constraints for testing purposes
one can call regulator_set_value_force function.
Signed-off-by: NKeerthy <j-keerthy@ti.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Let get_maintainers.pl pick up the new cmd/fdt.c.

Cc: Simon Glass <sjg@chromium.org>
Signed-off-by: NAndreas Färber <afaerber@suse.de>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Commit ec6617c3 includes autoconf.h in image-fit.c, causing conflict
for board odroid-xu3 which overwrites CONFIG_SYS_BOARD in header
file. Move the include higher and use linux/kconfig.h instead of
generated/autoconf.h.
Signed-off-by: NYork Sun <york.sun@nxp.com>
CC: Alison Wang <alison.wang@nxp.com>

To align with SPL change 38fed8ab and 693d4c9f, add Kconfig option
CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR to defconfig, and remove
CONFIG_SYS_U_BOOT_MAX_SIZE_SECTORS.
Signed-off-by: NYork Sun <york.sun@nxp.com>
CC: Feng Li <feng.li_2@nxp.com>

Add serial platform data to board file.
Enable driver model for PXA serial driver.
Signed-off-by: NMarcel Ziswiler <marcel.ziswiler@toradex.com>

With em humble DM and Kconfig migraters U-Boot binary size keeps
increasing. Drop a bunch of less needed stuff to save another precious
20+ KB.
Signed-off-by: NMarcel Ziswiler <marcel.ziswiler@toradex.com>