Provide easy helpers for reading integer, string and boolean values from
device-tree properties.
Signed-off-by: NSimon Glass <sjg@chromium.org>

The style is to use single quotes for strings where possible. Adjust this
function.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Add a way to find the byte offset of a property within the device tree. This
is only supported with the normal libfdt implementation since fdtget does
not provide this information.
Signed-off-by: NSimon Glass <sjg@chromium.org>

After any node/property deletion the device tree can be packed to remove
spare space. Add a way to perform this operation.

Note that for fdt_fallback, fdtput automatically packs the device tree after
deletion, so no action is required here.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Add support for deleting a device tree property. With the fallback
implementation this uses fdtput. With libfdt it uses the API call and
updates the offsets afterwards.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Since we want to be able to change the in-memory device tree using libfdt,
use a bytearray instead of a string. This makes interfacing from Python
easier.
Signed-off-by: NSimon Glass <sjg@chromium.org>

For binman we need to support deleting properties in the device tree. This
will change the offsets of nodes after the deletion. In preparation, add
code to keep track of when the offsets are invalid, and regenerate them.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This is not used anywhere in dtoc, so drop it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

If a source device tree is provide to the Fdt() constructors, compile it
automatically. This will be used in tests, where we want to build a
particular test .dts file and check that it works correctly in binman.
Signed-off-by: NSimon Glass <sjg@chromium.org>

When tools want to display information of varying levels of importance, it
helps to provide the user with control over the verbosity of these messages.
Progress messages work best if they are displayed and then removed from the
display when no-longer relevant.

Add a new tout library (terminal out) to handle these tasks.
Signed-off-by: NSimon Glass <sjg@chromium.org>

For tools which want to use input files and temporary output, it is useful
to have the handling of these dealt with in one place. Add a new library
which allows input files to be read, and output files to be written, all
based on a common directory structure.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Some functions have the same code in the subclasses. Move these into the
superclass to avoid duplication.
Signed-off-by: NSimon Glass <sjg@chromium.org>

These functions are identical in both subclasses. Move them into the base
class.

Note: In fact there is a bug in one version, which was fixed by this patch:

https://patchwork.ozlabs.org/patch/651697/Signed-off-by: NSimon Glass <sjg@chromium.org>

These functions are currently in a separate fdt_util file. Since they are
only used from PropBase and subclasses, it makes sense for them to be in the
PropBase class.

Move these functions into fdt.py along with the list of types.
Signed-off-by: NSimon Glass <sjg@chromium.org>

At present we have two separate implementations of the Fdt library, one which
uses fdtget/fdtput and one which uses libfdt (via swig).

Before adding more functionality it makes sense to create a base class for
these. This will allow common functions to be shared, and make the Fdt API
a little clearer.

Create a new fdt.py file with the base class, and adjust fdt_normal.py and
fdt_fallback.py to use it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

In preparation for creating an Fdt base class, rename this file to indicate
it is the normal Fdt implementation.
Signed-off-by: NSimon Glass <sjg@chromium.org>

Rather than have dtc worry about which fdt library to use, move this into
a helper file. Add a function which creates a new Fdt object and scans it,
regardless of the implementation.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This should be in with the other system includes. Move it.
Signed-off-by: NSimon Glass <sjg@chromium.org>

It is more useful to have this method raise an error when something goes
wrong. Make this the default and adjust the few callers that don't want to
use it this way.
Signed-off-by: NSimon Glass <sjg@chromium.org>

This complements the size/fatsize/ext4size commands added in
commit cf659819
load, save and ls are already implemented for hostfs, now tests can
cover the same operations on hostfs and emulated block devices.
Signed-off-by: NStefan Brüns <stefan.bruens@rwth-aachen.de>
Acked-by: NSimon Glass <sjg@chromium.org>

Signed-off-by: NStefan Brüns <stefan.bruens@rwth-aachen.de>
Acked-by: NSimon Glass <sjg@chromium.org>
Changed 'Sandbox' to 'sandbox' in subject:
Signed-off-by: NSimon Glass <sjg@chromium.org>

Import the latest version from the Diag software.

  - Support LD21 SoC (including DDR chips in the package)
  - Per-board granule adjustment for both reference and TV boards
  - Misc cleanups
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

Initialize the DPLL (PLL for DRAM) in SPL, and others in U-Boot
proper.  Split the common code into pll-base-ld20.c for easier
re-use.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

Now PLLs for DRAM controller are initialized in SPL, and the others
in U-Boot proper.  Setting up all of them in a single directory will
be helpful when we want to share code between SPL and U-Boot proper.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

The PLL for the DRAM interface must be initialized in SPL, but the
others can be delayed until U-Boot proper.  Move them from SPL to
U-Boot proper to save the precious SPL memory footprint.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

Basically, this should not be configured by users.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

This is the last code in the mach-uniphier/pinctrl/ directory.
Push the remaining code out to delete the directory entirely.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

Use the pin-mux data in the pinctrl drivers by directly calling
pinctrl_generic_set_state().
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

This will be needed for setting up the System Bus pin-mux via the
LD11/LD20 pinctrl driver.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

The NAND subsystem has not supported the Driver Model yet, but the
NAND pin-mux data are already in the pinctrl drivers.  Use them by
calling pinctrl_generic_set_state() directly.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

These settings are nicely cared by the pinctrl driver now.  Remove.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

This is enabled by default for all the supported boot modes.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

Now all UniPhier SoCs support a pinctrl driver.  Select (SPL_)PINCTRL
since it is mandatory even for base use.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

DT-side updates to make pinctrl on sLD3 SoC really available.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

Add pin-mux support for UniPhier sLD3 SoC.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

On LD4 SoC or later, the pin-mux registers are 8bit wide, while 4bit
wide on sLD3 SoC.  Support it for the sLD3 pinctrl driver.
Signed-off-by: NMasahiro Yamada <yamada.masahiro@socionext.com>

Sinlinx SinA33 has a USB OTG port, but VBUS is controlled manually from
a jumper pad.

Enable OTG in gadget mode, as well as the download gadget and related
functions.
Signed-off-by: NChen-Yu Tsai <wens@csie.org>
Reviewed-by: NHans de Goede <hdegoede@redhat.com>
Signed-off-by: NHans de Goede <hdegoede@redhat.com>