14 Sep, 2018
1 commit
-
Instead of keeping a custom environment, use a more generic approach
by switching to distro config.Signed-off-by: Fabio Estevam
Signed-off-by: Otavio Salvador
11 Sep, 2018
28 commits
-
Add the minimum dt nodes required to boot. These nodes
will get deleted as kernel gets these nodes added in the
main dts files.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla -
Create a basic U-Boot environment that allows the automatic loading
of a Linux Kernel located at /boot/Image and an associated device tree
blob located at /boot/k3-am654-base-board.dtb from the secondary
partition of an ext4-formatted SD card on the AM654x EVM. Furthermore
the boot.scr and uEnv.txt detection and loading schemes are supported
in a manner already known from other TI platforms.Note that this is intended to be a starting point to enable initial
board use and will most certainly get extended and refactored as
different boot media become available.Reviewed-by: Tom Rini
Signed-off-by: Andreas Dannenberg
Signed-off-by: Lokesh Vutla -
Add initial support for AM654 based EVM running on A53. Enable
4GB of DDR available on the EVM so that kernel DTB file
can be updated accordingly.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla
[Andreas: Added 4GB ddr support]
Signed-off-by: Andreas Dannenberg -
Existing rproc_init() api tries to initialize all available
remoteproc devices. This will fail when there is dependency
among available remoteprocs. So introduce a separate api
that allows to initialize remoteprocs individually based
on id.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla -
Secure Proxy module manages hardware threads that are meant
for communication between the processor entities. Adding
support for this driver.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla
Signed-off-by: Andreas Dannenberg -
Sometimes mbox controllers wants to store private data in
mbox_chan so that it can be used at a later point of time.
Adding support for hooking private data.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla -
There are cases where there are more than one power domain
attached to the device inorder to get the device functional.
So add support for enabling power domain based on the index.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla -
Some systems require more than a single ID to identify and configure any
clock provider. For those scenarios add an optional data field to the
clock control structure.Reviewed-by: Tom Rini
Signed-off-by: Andreas Dannenberg
Signed-off-by: Lokesh Vutla -
Some systems require more than a single ID to identify and configure any
reset provider. For those scenarios add an optional data field to the
reset control structure.Reviewed-by: Tom Rini
Signed-off-by: Andreas Dannenberg
Signed-off-by: Lokesh Vutla -
Add a reset operations function pointer to support querying the current
status of a reset control.Reviewed-by: Tom Rini
Signed-off-by: Andreas Dannenberg
Signed-off-by: Lokesh Vutla -
TI-SCI message protocol provides support for controlling of various
physical cores available in SoC. In order to control which host is
capable of controlling a physical processor core, there is a processor
access control list that needs to be populated as part of the board
configuration data.Introduce support for the set of TI-SCI message protocol apis that
provide us with this capability of controlling physical cores.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla -
Since system controller now has control over SoC power management, it
needs to be explicitly requested to reboot the SoC. Add support for
it.Reviewed-by: Tom Rini
Signed-off-by: Andreas Dannenberg
Signed-off-by: Lokesh Vutla
Signed-off-by: Nishanth Menon -
In general, we expect to function at a device level of abstraction,
however, for proper operation of hardware blocks, many clocks directly
supplying the hardware block needs to be queried or configured.Introduce support for the set of SCI message protocol support that
provide us with this capability.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla
Signed-off-by: Nishanth Menon -
TI-SCI message protocol provides support for management of various
hardware entitites within the SoC. Introduce the fundamental
device management capability support to the driver protocol
as part of this change.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla
Signed-off-by: Nishanth Menon -
TI-SCI message protocol provides support for board configuration
to assign resources and other board related operations.
Introduce the board configuration capability support to the driver protocol
as part of this change.Reviewed-by: Tom Rini
Signed-off-by: Andreas Dannenberg
Signed-off-by: Lokesh Vutla -
Texas Instrument's System Control Interface (TI SCI) message protocol is
used in Texas Instrument's System on Chip (SoC) such as those in the K3
family AM654 SoC to communicate between various compute processors with
a central system controller entity.The TI SCI message protocol provides support for management of various
hardware entities within the SoC. Add support driver to allow
communication with system controller entity within the SoC using the
mailbox client.This is mostly derived from the TI SCI driver in Linux located at
drivers/firmware/ti_sci.c.Reviewed-by: Tom Rini
Signed-off-by: Lokesh Vutla
Signed-off-by: Nishanth Menon
Signed-off-by: Andreas Dannenberg -
With the migration to distro-boot, the size of the U-Boot proper
image for uniphier_v7_defconfig exceeded the current limit, 576KB.
Increase it to 832KB.CONFIG_SYS_UBOOT_BASE must be moved as well to avoid the image
over-wrap because the boot ROM of Pro4, Pro5, PXs2/LD6b loads
the SPL to the physical address 0x100000.Signed-off-by: Masahiro Yamada
-
This patch enables DM_SERIAL for the pandora board. Verified that
the default kernel can still be booted with this.Signed-off-by: Grazvydas Ignotas
-
Add support for loading U-Boot on the Broadcom 7260 SoC. This port
assumes Broadcom's BOLT bootloader is acting as the second stage
bootloader, and U-Boot is acting as the third stage bootloader, loaded
as an ELF program by BOLT.Signed-off-by: Thomas Fitzsimmons
Reviewed-by: Florian Fainelli
Cc: Florian Fainelli -
Change the configured serial console index to reflect that it is the
first physical UART, reorder some defconfig lines and move some
environment configuration from bcmstb.h to bcm7445.h.Signed-off-by: Thomas Fitzsimmons
Cc: Florian Fainelli -
Add HS400 support.
Selecting HS400 needs first select HS200 according to spec, so use
a dedicated function for HS400.
Add HS400 related macros.
Remove the restriction of only using the low 6 bits of
EXT_CSD_CARD_TYPE, using all the 8 bits.Signed-off-by: Peng Fan
Cc: Jaehoon Chung
Cc: Jean-Jacques Hiblot
Cc: Stefano Babic
Cc: Kishon Vijay Abraham I
Cc: Faiz Abbas
Cc: Marek Vasut
Signed-off-by: Peng Fan -
In int-ll64.h, we always use the following typedefs:
typedef unsigned int u32;
typedef unsigned long uintptr_t;
typedef unsigned long long u64;This does not need to match to the compiler's .
Do not include it.The use of PRI* makes the code super-ugly. You can simply use
"l" for printing uintptr_t, "ll" for u64, and no modifier for u32.Signed-off-by: Masahiro Yamada
-
All architectures have the same definition for s8/16/32/64
and u8/16/32/64.Factor out the duplicated code into .
BTW, Linux unified the kernel space definition into int-ll64.h
a few years ago as you see in Linux commit 0c79a8e29b5f
("asm/types.h: Remove include/asm-generic/int-l64.h").Signed-off-by: Masahiro Yamada
-
You do not need to use the typedefs provided by compiler.
Our compilers are either IPL32 or LP64. Hence, U-Boot can/should
always use int-ll64.h typedefs like Linux kernel, whatever the
typedefs the compiler internally uses.Signed-off-by: Masahiro Yamada
-
Signed-off-by: Patrice Chotard
Reviewed-by: Simon Glass -
setparity users has been updated to use new setconfig ops,
so we can safely remove setparity opsSigned-off-by: Patrice Chotard
Reviewed-by: Simon Glass -
Replace setparity by more generic setconfig ops
to allow uart parity, bits word length and stop bits
number change.Adds SERIAL_GET_PARITY/BITS/STOP macros.
Signed-off-by: Patrick Delaunay
Signed-off-by: Patrice Chotard
Reviewed-by: Simon Glass
06 Sep, 2018
1 commit
-
When booting the QEMU virt machine with -net nic,model=e1000 we can already
support network boot just fine today.So let's enable the default bootcmd to also evaluate DHCP responses properly.
That way we can enable network boot seamlessly with the virt target.Signed-off-by: Alexander Graf
05 Sep, 2018
1 commit
04 Sep, 2018
5 commits
-
This commit adds support for the Toradex Colibri iMX7D 1GB Computer
on Module. The module is very similar to the Colibri iMX7D 512MB
but uses eMMC instead of raw NAND. This patch introduces a new
board specific Kconfig symbol to select between the two flash
options.Signed-off-by: Stefan Agner
-
CONFIG_BOOTDELAY has been migrated to Kconfig, but cl-som-imx7 was
missed. We can just delete the assignments as the config already has
the correct value.Signed-off-by: Alex Kiernan
-
Convert the codes and configurations to enable DM drivers in u-boot for
modules: i2c, PMIC, regulator, USB, Ethernet, SD/MMC, GPIO and QSPIThis patch does not change SPL, so it still uses non-DM driver for
UART, GPIO and SD/MMC.Signed-off-by: Ye Li
-
On iMX7D SabreSD board, the QSPI has pins conflict with EPDC (default).
To use QSPI, users have to rework the board (de-populate R388-R391, R396-R399
populate R392-R395, R299, R300). So we add new DTS file and new defconfig
dedicated for QSPI.Other changes to support the DM QSPI:
- Add QSPI node and alias spi0.
- Modify spi4 (spi-gpio) node and add alias spi5 for it to avoid req
conflict
- Add EPDC node in imx7d.dtsi and disable it in imx7d-sdb-qspi.dts to
align with kernel and also present the conflict.
- Add -u-boot.dtsi to modify compatible string of mx25l51245g@0 to
"spi-flash"
- Remove iomux settings of qspi in board codes which is not needed
for DM driver.Signed-off-by: Ye Li
-
To support DM QSPI driver
- Add spi0 and spi1 alias for qspi1 and qspi2.
- Add -u-boot.dtsi to modify n25q256a@0 and n25q256a@1 compatible string
to "spi-flash" and add "num-cs" property.
- Enable DM SPI/QSPI relavent configurations
- Remove iomux settings of qspi2 in board codes which is not needed
for DM driver.
- Add sf default settings. So running "sf probe" can detect the flashSigned-off-by: Ye Li
31 Aug, 2018
1 commit
-
argc = 1: all tests are run
argc > 1: only argv[1] is runSo we need argc >= 1.
Signed-off-by: Heinrich Schuchardt
Reviewed-by: Simon Glass
30 Aug, 2018
3 commits
-
Now that we have full Linux kernel boot support on EFI payload,
avoid pass "acpi=off" to the kernel command line.Signed-off-by: Bin Meng
Reviewed-by: Simon Glass -
At present Linux kernel loaded from U-Boot as an EFI payload does
not boot. This fills in kernel's boot params structure with the
required critical EFI information like system table address and
memory map stuff so that kernel can obtain essential data like
runtime services and ACPI table to boot.With this patch, now U-Boot as an EFI payload becomes much more
practical: it is another option of kernel bootloader, ie, can be
a replacement for grub.Signed-off-by: Bin Meng
Reviewed-by: Simon Glass
