Use dev_read_addr_ptr() instead of devfdt_get_addr() so that we can support
live DT.
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
Reviewed-by: NRamon Fried <rfried.dev@gmail.com>

The fdtdec.h is no use in this file, remove the include code.
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>

- Update a few MAINTAINERS entries
- cache alignment fix in ext4 code
- Two small test fixes

%s/decopmression/decompression/
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Signed-off-by: NMarek Behún <marek.behun@nic.cz>

We need to align the cache buffer to ARCH_DMA_MINALIGN in order to avoid
access errors like

CACHE: Misaligned operation at range [be0231e0, be0235e0]

seen on the MCIMX7SABRE.

Fixes: d5aee659 ("fs: ext4: cache extent data")
Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
Reviewed-by: NTom Rini <trini@konsulko.com>
Reviewed-by: NStephen Warren <swarren@nvidia.com>
Tested-by: NPeter Robinson <pbrobinson@gmail.com>

Add usb.h file into the USB list.
Signed-off-by: NMarek Vasut <marex@denx.de>
Cc: Tom Rini <trini@konsulko.com>

Commit 41e30dcf ("cmd: mmc: Make Mode: printout consistent") fixed
the layout of `mmc info` output.  Reflect this change in the respective
testcase.

Also fix a typo in the documentation.

Fixes: 41e30dcf ("cmd: mmc: Make Mode: printout consistent")
Signed-off-by: NHarald Seiler <hws@denx.de>
Acked-by: NStephen Warren <swarren@nvidia.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Currently this causes failures of the platform when running the EFI
loader tests, so disable it for now.

This reverts commit af827140.
Signed-off-by: NTom Rini <trini@konsulko.com>

- Fixed for rv1108 and elgin-rv1108 board
- Fix the keyboard from USB instead of CrOS EC

Depending on the SoC, a header of four characters is prepended to the
image. There is already a macro defining the number of characters:
RK_SPL_HDR_SIZE, so use it instead of hardcoding "4".
Signed-off-by: NMiquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Since commit 79030a48 ("rockchip: Add Single boot image
(with binman, pad_cat)") the following boot regression is seen:

U-Boot 2020.04-rc3-00050-gd16e18ca-dirty (Mar 09 2020 - 11:40:07 -0300)

Model: Elgin RV1108 R1 board
DRAM:  128 MiB
initcall sequence 67fd12a0 failed at call 6000b927 (err=-22)

This happens because the above commit missed to include the
"rockchip-u-boot.dtsi" for rv1108, so include this file
like it done for other Rockchip SoC dtsi's.

Fixes: 79030a48 ("rockchip: Add Single boot image (with binman, pad_cat)")
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Currently the following error message is seen during boot:

U-Boot 2020.01-08751-g55759ae141 (Mar 09 2020 - 14:44:52 -0300)

Model: Elgin RV1108 R1 board
DRAM:  128 MiB
APLL: 600000000 DPLL:1200000000 GPLL:1188000000
ACLK_BUS: 148500000 ACLK_PERI:148500000 HCLK_PERI:148500000 PCLK_PERI:74250000
MMC:   dwmmc@30110000: 0
Loading Environment from MMC... OK
In:    serial@10210000
Out:   serial@10210000
Err:   serial@10210000
Model: Elgin RV1108 R1 board
rockchip_dnl_key_pressed: adc_channel_single_shot fail!
....

Since the elgin-rv1108 does not use ADC to read the download
key status, select CONFIG_ROCKCHIP_BOOT_MODE_REG=0 to avoid
such error.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Since commit 8e9a8d0d ("rockchip: elgin-rv1108: use board_early_init_f
for per-boar init") the function that configure the board GPIOs is no
longer called since CONFIG_BOARD_EARLY_INIT_F=y is not selected.

These GPIOs do not need to be configured in such early stagem, so change it
to rk_board_late_init() and also select CONFIG_BOARD_LATE_INIT=y
to fix the regression.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>
Signed-off-by: NFabio Berton <fabio.berton@ossystems.com.br>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

In order to make the console pins more robust to noise, activate
the pullups and increase its drive strength.
Signed-off-by: NOtavio Salvador <otavio@ossystems.com.br>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

These boards aren't ChromeOS devices so won't have a cros-ec-keyb
input as it's the keyboard available via the ChromeOS Embedded
Controller. Update them to use a USB keyboard which would actually
be available. Also enable the usb keyboard option for those devices
that don't have it enabled already.
Signed-off-by: NPeter Robinson <pbrobinson@gmail.com>
Reviewed-by: NMichael Trimarchi <michael@amarulasolutions.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Use syscon API to get grf base instead of get from dts.
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>

Use syscon API to get grf base instead of get from dts.
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>
Reviewed-by: NSimon Glass <sjg@chromium.org>
Acked-by: NOtavio Salvador <otavio@ossystems.com.br>

EFI was disabled in f95b8a4b because of the missing DTB file,
and indeed, the DTB file is required to load recent versions of GRUB
(2.04) correctly.
Signed-off-by: NKristian Amlie <kristian.amlie@northern.tech>

Pull request for UEFI sub-system for efi-2020-04-rc4 (5)

This series contains bug fixes for the UEFI sub-system:

* report correct variable length in GetNextVariable()
* correct copying direction if freestanding memmove()
* remove const for parameter of GetNextVariableName()
* correct function descriptions

Unit tests are added and adjusted.

'vendor' is both an input and an output parameter. So it cannot be
constant.

Fixes: 0bda81bf ("efi_loader: use const efi_guid_t * for variable services")
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

Provide unit tests for CalculateCrc32(), CopyMem(), SetMem().
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

For EFI binaries we have to provide an implementation of memmove() in
efi_freestanding.c.

Before this patch the memmove() function was copying in the wrong
direction.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

Correct the description of function efi_convert_pointer().
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

To check if a variable is non-zero there is no need for '!= 0'.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

GetNextVariableName should report the length of the variable including the
final 0x0000 in bytes.

Check this in the unit test.

Increase the buffer size for variable names. 40 bytes is too short.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

The runtime service GetNextVariable() returns the length of the next
variable including the closing 0x0000. This length should be in bytes.

Comparing the output of EDK2 and U-Boot shows that this is currently not
correctly implemented:

EDK2:
OsIndicationsSupported: 46
PlatformLang: 26
PlatformLangCodes: 36

U-Boot:
OsIndicationsSupported: 23
PlatformLang: 13
PlatformLangCodes: 18

Provide correct length in GetNextVariable().

Fixes: d99a87f8 ("efi_loader: implement GetNextVariableName()")
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

Use Sphinx style for function descriptions.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

Correct the file description.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

- Revert "sunxi: psci: avoid error address-of-packed-member"

Pull request for UEFI sub-system for efi-2020-04-rc4 (4)

This series fixes several bugs:

* consider the /reserved-memory node in the device tree
* consider memory reservations created in ft_board_setup()
* correct output of 'efidebug memmap' on the sandbox
* correct the definition of efi_capsule_header()

Furthermore some definitions needed for future patches are added to
header files.

- Fix sbi_remote_sfence_vma{,_asid}.
- Avoid calling sbi_clear_ipi().
- Add new SBI v0.2 extensions support.

Using memcpy() for some MMIO access is generally frowned upon and might
break things on some platforms. Allwinner H3, which fails to boot, being
an example here.

Moreover, fields being accessed are naturally aligned and warnings
produced by GCC have been quiesced for some time already by:

53dc8ae6 ("gcc-9: silence 'address-of-packed-member' warning")

That said, it should be okay to revert this commit.

This reverts commit 9bd34a69.

Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: NTomasz Duszynski <tduszyns@gmail.com>
Acked-by: NJagan Teki <jagan@amarulasolutions.com>

See UEFI specification, section 8.5.3.
In addition, the structure, efi_capsule_header, should be "packed"
as it is a serialized binary format in a capsule file.
Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>

This is a preparatory patch.
Those functions will be used in an implementation of UEFI firmware
management protocol as part of my capsule update patch.
Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>

Some of those values will be used in an implementation of UEFI firmware
management protocol as part of my capsule update patch.
Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>

These flags are expected to be set in OsIndicationsSupported variable
if corresponding features are supported. See UEFI specification,
section 8.5.4.

In particular, capsule-related flags will be used in my capsule
update patch.
Signed-off-by: NAKASHI Takahiro <takahiro.akashi@linaro.org>

Fix misspelled EFI_OS_INDICATIONS_BOOT_TO_FW_UI.
Reviewed-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

Currently, bootefi only parses memory reservation block to setup
EFI reserved memory mappings. However, it doesn't parse the
reserved-memory[1] device tree node that also can contain the
reserved memory regions.

Add capability to parse reserved-memory node and update the EFI memory
mappings accordingly.

1. <U-Boot source>/doc/device-tree-bindings/reserved-memory/reserved-memory.txt]
Signed-off-by: NAtish Patra <atish.patra@wdc.com>

Fix an endless loop.

The /reserved-memory node may have children without reg property. Remove
a superfluous debug statement.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

Addresses in the sandbox's device tree are in the sandbox's virtual address
space. If we want to compare memory reservations in the device-tree with
the output of 'efidebug memmap', we need to convert back to this address
space.

Adjust the output of the 'efidebug memmap' command.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>

Some memory reservations are made in ft_board_setup(). Ensure that we
create reserved memory map entries after ft_board_setup().

The downside of this patch is that if bootefi is called multiple times with
an devicetree argument superfluous reservations for the old copies of the
device tree will exist. But that is still better than missing a reservation.

Deleting the superfluous reservations is not possible because reservations
in the memory map are rounded to page size and may be coallesced.
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>