| #
0e00a84c |
| 04-Mar-2018 |
Masahiro Yamada <yamada.masahiro@socionext.com> |
UPSTREAM: libfdt: move headers to <linux/libfdt.h> and <linux/libfdt_env.h>
Thomas reported U-Boot failed to build host tools if libfdt-devel package is installed because tools include libfdt header
UPSTREAM: libfdt: move headers to <linux/libfdt.h> and <linux/libfdt_env.h>
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 <libfdt.h> -> #include <linux/libfdt.h> #include <libfdt_env.h> -> #include <linux/libfdt_env.h>
Change-Id: I6c0f7e50e8b571106627f25ddac008a62bd2994e Reported-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
show more ...
|
| #
e71e2cea |
| 13-Nov-2017 |
Simon Glass <sjg@chromium.org> |
UPSTREAM: dtoc: Fix up tests
The tool has changed slightly since it was originally written. Update the tests to suit.
Change-Id: I6935a7c4cc16e1a3e5c617133b12d1982e640c74 Signed-off-by: Simon Glass
UPSTREAM: dtoc: Fix up tests
The tool has changed slightly since it was originally written. Update the tests to suit.
Change-Id: I6935a7c4cc16e1a3e5c617133b12d1982e640c74 Signed-off-by: Simon Glass <sjg@chromium.org> Signed-off-by: Kever Yang <kever.yang@rock-chips.com> (cherry picked from commit aab660fe18ac24ee859a203f517f939685af5e10)
show more ...
|
| #
54d1a4b7 |
| 29-Aug-2017 |
Simon Glass <sjg@chromium.org> |
dtoc: Support properties containing multiple phandle values
At present dtoc has a very simplistic view of phandles. It assumes that a property has only a single phandle with a single argument (i.e.
dtoc: Support properties containing multiple phandle values
At present dtoc has a very simplistic view of phandles. It assumes that a property has only a single phandle with a single argument (i.e. two cells per property).
This is not true in many cases. Enhance the implementation to scan all phandles in a property and to use the correct number of arguments (which can be 0, 1, 2 or more) when generating the C code. For the struct definitions, use a struct which can hold the maximum number of arguments used by the property.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
f9faa230 |
| 29-Aug-2017 |
Simon Glass <sjg@chromium.org> |
dtoc: Put phandle args in an array
We want to support more than one phandle argument. It makes sense to use an array for this rather than discrete struct members. Adjust the code to support this. Re
dtoc: Put phandle args in an array
We want to support more than one phandle argument. It makes sense to use an array for this rather than discrete struct members. Adjust the code to support this. Rename the member to 'arg' instead of 'id'.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
59e6856d |
| 29-Aug-2017 |
Simon Glass <sjg@chromium.org> |
dtoc: Put each phandle on a separate line
When writing values from properties which contain phandles, dtoc currently writes 8 phandles per line. Change this to write one phandle per line. This helps
dtoc: Put each phandle on a separate line
When writing values from properties which contain phandles, dtoc currently writes 8 phandles per line. Change this to write one phandle per line. This helps reduce line length, since phandles are generally longer and may have arguments.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
3a40acd4 |
| 29-Aug-2017 |
Simon Glass <sjg@chromium.org> |
dtoc: Rename the phandle struct
Rather than naming the phandle struct according to the number of cells it uses (e.g. struct phandle_2_cell) name it according to the number of arguments it has (e.g.
dtoc: Rename the phandle struct
Rather than naming the phandle struct according to the number of cells it uses (e.g. struct phandle_2_cell) name it according to the number of arguments it has (e.g. struct phandle_1_arg). This is a more intuitive naming.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
4b26144b |
| 29-Aug-2017 |
Simon Glass <sjg@chromium.org> |
dtoc: Handle 'reg' properties with unusual sizes
At present dtoc assumes that all 'reg' properties have both an address and a size. For I2C devices we do not have this. Adjust dtoc to cope.
Reporte
dtoc: Handle 'reg' properties with unusual sizes
At present dtoc assumes that all 'reg' properties have both an address and a size. For I2C devices we do not have this. Adjust dtoc to cope.
Reported-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
a28bfcc3 |
| 29-Aug-2017 |
Simon Glass <sjg@chromium.org> |
dtoc: Add support for 32 or 64-bit addresses
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.
Updat
dtoc: Add support for 32 or 64-bit addresses
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 <sjg@chromium.org>
Suggested-by: Heiko Stuebner <heiko@sntech.de> Reported-by: Kever Yang <kever.yang@rock-chips.com>
show more ...
|
| #
12a972ef |
| 29-Aug-2017 |
Simon Glass <sjg@chromium.org> |
dtoc: Avoid very long lines in output
Large arrays can result in lines with hundreds or thousands of characters which is not very editor-friendly. To avoid this, addjust the tool to group values 8 p
dtoc: Avoid very long lines in output
Large arrays can result in lines with hundreds or thousands of characters which is not very editor-friendly. To avoid this, addjust the tool to group values 8 per line.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
8d3a2568 |
| 12-Jul-2017 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-dm
|
| #
c0791928 |
| 19-Jun-2017 |
Simon Glass <sjg@chromium.org> |
dtoc: Add tests
Add some tests of dtoc's functionality to make it easier to expand and enhance the tool.
Signed-off-by: Simon Glass <sjg@chromium.org>
|