u-boot.git/include/fdtdec.h, branch v2018.03

libfdt: move headers to and

2018-03-05T15:16:28+00:00

Thomas reported U-Boot failed to build host tools if libfdt-devel
package is installed because tools include libfdt headers from
/usr/include/ instead of using internal ones.

This commit moves the header code:
  include/libfdt.h         -> include/linux/libfdt.h
  include/libfdt_env.h     -> include/linux/libfdt_env.h

and replaces include directives:
  #include       -> #include 
  #include   -> #include 

Reported-by: Thomas Petazzoni 
Signed-off-by: Masahiro Yamada

sandbox: Add 64-bit sandbox

2018-02-18T22:53:48+00:00

To debug device tree issues involving 32- and 64-bit platforms, it is useful to
have a generic 64-bit platform available.

Add a version of the sandbox that uses 64-bit integers for its physical
addresses as well as a modified device tree.

Signed-off-by: Mario Six 
Added CONFIG_SYS_TEXT_BASE to configs/sandbox64_defconfig
Signed-off-by: Simon Glass

fdtdec: allow board to provide fdt for CONFIG_OF_SEPARATE

2018-01-15T21:29:03+00:00

Similar to CONFIG_OF_BOARD, but in this case the fdt is still built by
u-boot build.  This allows the board to patch the fdt, etc.

In the specific case of dragonboard 410c, we pass the u-boot generated
fdt to the previous stage of bootloader (by embedding it in the
u-boot.img that is loaded by lk/aboot), which patches the fdt and passes
it back to u-boot.

Signed-off-by: Rob Clark 
[trini: Update board_fdt_blob_setup #if check]
Signed-off-by: Tom Rini

fdt: Add compatible strings for Arria 10

2017-11-26T01:34:10+00:00

Add compatible strings for Intel Arria 10 SoCFPGA device.

Signed-off-by: Tien Fong Chee

dtoc: Add support for 32 or 64-bit addresses

2017-09-15T11:27:38+00:00

When using 32-bit addresses dtoc works correctly. For 64-bit addresses it
does not since it ignores the #address-cells and #size-cells properties.

Update the tool to use fdt64_t as the element type for reg properties when
either the address or size is larger than one cell. Use the correct value
so that C code can obtain the information from the device tree easily.

Alos create a new type, fdt_val_t, which is defined to either fdt32_t or
fdt64_t depending on the word size of the machine. This type corresponds
to fdt_addr_t and fdt_size_t. Unfortunately we cannot just use those types
since they are defined to phys_addr_t and phys_size_t which use
'unsigned long' in the 32-bit case, rather than 'unsigned int'.

Add tests for the four combinations of address and size values (32/32,
64/64, 32/64, 64/32). Also update existing uses for rk3399 and rk3368
which now need to use the new fdt_val_t type.

Signed-off-by: Simon Glass 

Suggested-by: Heiko Stuebner 
Reported-by: Kever Yang 
Reviewed-by: Philipp Tomsich 
Tested-by: Kever Yang

fdtdec: Drop old compatible values

2017-07-28T18:02:48+00:00

These are not needed now since the drivers now use driver model. Drop
them.

Signed-off-by: Simon Glass 
Tested-by: Marcel Ziswiler 
Tested-on: Beaver, Jetson-TK1
Tested-by: Stephen Warren

cros_ec: Convert to support live tree

2017-06-01T13:03:11+00:00

Convert this driver to support the live device tree and remove the old
fdtdec support.

The keyboard is not yet converted.

Signed-off-by: Simon Glass

dm: core: Add a place to put extra device-tree reading functions

2017-06-01T13:03:07+00:00

Some functions deal with structured data rather than simple data types.
It makes sense to have these in their own file. For now this just has a
function to read a flashmap entry. Move the data types also.

Signed-off-by: Simon Glass

edid: Add HDMI flag to timing info

2017-05-15T18:32:12+00:00

Some DVI monitors don't show anything in HDMI mode since audio stream
confuses them. To solve this situation, this commit adds HDMI flag in
timing data and sets it accordingly during edid parsing.

First existence of extension block is checked. If it exists and it is
CEA861 extension, then data blocks are checked for presence of HDMI
vendor specific data block. If it is present, HDMI flag is set.

Signed-off-by: Jernej Skrabec 
Reviewed-by: Simon Glass

Allow boards to initialize the DT at runtime.

2017-05-10T00:35:06+00:00

In some boards like the Raspberry Pi the initial bootloader will pass
a DT to the kernel. When using U-Boot as such kernel, the board code in
U-Boot should be able to provide U-Boot with this, already assembled
device tree blob.

This patch introduces a new config option CONFIG_OF_BOARD to use instead
of CONFIG_OF_EMBED or CONFIG_OF_SEPARATE which will initialize the DT
from a board-specific funtion instead of bundling one with U-Boot or as
a separated file. This allows boards like the Raspberry Pi to reuse the
device tree passed from the bootcode.bin and start.elf firmware
files, including the run-time selected device tree overlays.

Signed-off-by: Alex Deymo 
Reviewed-by: Simon Glass