Skip to content

Integrate u-boot-seco-rk/seco_2017.09_next_develop_pre-reloc_ym

GitBot requested to merge u-boot-seco_2017_09_next/seco_2017.09_next_develop_pre-reloc_ym into kirkstone

Commit: edgehog/bsp/rockchip/u-boot-seco-rk@d6292cc1

[DTS][PINCONF] Make every pin configuration available pre-relocation

To use any peripheral in pre-relocation we need to use its pinctrl, and so we need pin configurations; u-boot,dm-pre-reloc it's used to make them available before relocation.

--

Commit: edgehog/bsp/rockchip/u-boot-seco-rk@3aaf2021

[PINCTRL] Avoid using LIVETREE when setting pinctrl configuration

rockchip_pinctrl_set_state tries to use LVETREE when OF_LIVE is enabled. There are however some cases when OF_LIVE is enabled by the LIVETRE is not yet ready (for example in pre-relocation contexts). Prefer always using the FDT blob.

--

Commit: edgehog/bsp/rockchip/u-boot-seco-rk@60291b6e

[FIT] Do not use external data when generating fit-dtb.blob

-E option is used to place data outside the FIT image (usually appended at the end of it). This works fine when the image is generated from a .its file, but without it (auto format), it causes problems. In particular, the scripts fail to compute correctly the data offset, causing the resulting FIT to be non-functional. We prefer to use embedded data instead.

--

Commit: edgehog/bsp/rockchip/u-boot-seco-rk@7178b888

[FIT] Improve DTB location if FIT

fdt_offset() looks for "data-offset" property inside the DTB node. This property can be absent when the FIT is generated without -E option (external data). In this case, DTB data is inside the FIT rather than appended to it. Using fit_image_get_data we can retrieve the DTB regardless of its position.

--

Commit: edgehog/bsp/rockchip/u-boot-seco-rk@36b9ec75

[FIT] Include multiple DTB blob inside FIT when using CONFIG_MULTI_DTB_FIT

Rockchip scripts for FIT node generation are used to generate u-boot.its; this file is then used to generate u-boot FIT image. When using CONFIG_MULTI_DTB_FIT we need to insert multiple DTB blob (fit-dtb.blob) in the place of u-boot.dtb. This blob is again a FIT image, containing all the possible DTBs for the board, listed in CONFIG_OF_LIST.

Merge request reports