diff options
author | Tom Rini <trini@konsulko.com> | 2018-07-20 22:35:49 -0400 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2018-07-20 22:35:49 -0400 |
commit | 83853366e3f9eb76426a6b1bda810e470bce04f0 (patch) | |
tree | 4e99633bca0ae2479b46f0e2885775aea5995e2d /doc | |
parent | e0ed8332fa2fe684b4c8ba1caab991663730cbf0 (diff) | |
parent | a2a5053a15e4059c7445737d60f7b8425ca863f8 (diff) |
Merge branch 'master' of git://git.denx.de/u-boot-rockchip
Diffstat (limited to 'doc')
-rw-r--r-- | doc/README.rockchip | 8 | ||||
-rw-r--r-- | doc/device-tree-bindings/chosen.txt | 10 |
2 files changed, 14 insertions, 4 deletions
diff --git a/doc/README.rockchip b/doc/README.rockchip index d35071d653..51b00a9d85 100644 --- a/doc/README.rockchip +++ b/doc/README.rockchip @@ -124,11 +124,11 @@ something like: => The rockchip bootrom can load and boot an initial spl, then continue to -load a second-level bootloader(ie. U-BOOT) as soon as it returns to bootrom. -Therefore RK3288 has another loading sequence like RK3036. The option of -U-Boot is controlled with this setting in U-Boot: +load a second-stage bootloader (ie. U-Boot) as soon as the control is returned +to the bootrom. Both the RK3288 and the RK3036 use this special boot sequence. +The configuration option enabling this is: - #define CONFIG_SPL_ROCKCHIP_BACK_TO_BROM + CONFIG_SPL_ROCKCHIP_BACK_TO_BROM=y You can create the image via the following operations: diff --git a/doc/device-tree-bindings/chosen.txt b/doc/device-tree-bindings/chosen.txt index c96b8f7109..da7b4e6c45 100644 --- a/doc/device-tree-bindings/chosen.txt +++ b/doc/device-tree-bindings/chosen.txt @@ -73,3 +73,13 @@ Example u-boot,spl-boot-order = "same-as-spl", &sdmmc, "/sdhci@fe330000"; }; }; + +u-boot,spl-boot-device property +------------------------------- + +This property is a companion-property to the u-boot,spl-boot-order and +will be injected automatically by the SPL stage to notify a later stage +of where said later stage was booted from. + +You should not define this property yourself in the device-tree, as it +may be overwritten without warning. |