| #
2ee484fa |
| 12-May-2023 |
Joseph Chen <chenjh@rock-chips.com> |
common: image: Print '/reserved-memory' regions after board fdt fixup
Signed-off-by: Joseph Chen <chenjh@rock-chips.com> Change-Id: I0512c8af34f0581f5e01f3dd8aa0fb1e3724fe1f
|
| #
4e7cb295 |
| 05-Nov-2021 |
Joseph Chen <chenjh@rock-chips.com> |
lib: bootm-fdt: fix compile error when not set CONFIG_ARCH_FIXUP_FDT_MEMORY
Showing memory banks is helpful.
Signed-off-by: Joseph Chen <chenjh@rock-chips.com> Change-Id: I07aa5ae727d52b22e6034c193
lib: bootm-fdt: fix compile error when not set CONFIG_ARCH_FIXUP_FDT_MEMORY
Showing memory banks is helpful.
Signed-off-by: Joseph Chen <chenjh@rock-chips.com> Change-Id: I07aa5ae727d52b22e6034c1935f133d3b9fd9b71
show more ...
|
| #
1a4f6af8 |
| 02-Mar-2020 |
Joseph Chen <chenjh@rock-chips.com> |
Merge branch 'next-dev' into thunder-boot
|
| #
470c5092 |
| 12-Dec-2019 |
Joseph Chen <chenjh@rock-chips.com> |
board_f/arm: fixup 4GB+ memory size
- fixup gd->bd->bi_dram[] before update "/memory" node - append 4GB+ memory size when announce dram
Signed-off-by: Joseph Chen <chenjh@rock-chips.com> Change-Id:
board_f/arm: fixup 4GB+ memory size
- fixup gd->bd->bi_dram[] before update "/memory" node - append 4GB+ memory size when announce dram
Signed-off-by: Joseph Chen <chenjh@rock-chips.com> Change-Id: I8908426c54d251e5cfa9216b0dc5470145e37cb5
show more ...
|
| #
6bccab87 |
| 31-Jul-2019 |
Joseph Chen <chenjh@rock-chips.com> |
fdt: fixup: move board_fdt_fixup the earliest than others
If we update fdt by create or move operation, the fdt nodes offset are changed, but device node of DM didn't update its offset linking with
fdt: fixup: move board_fdt_fixup the earliest than others
If we update fdt by create or move operation, the fdt nodes offset are changed, but device node of DM didn't update its offset linking with the fdt node. This makes driver can't parse the right fdt node info.
This is a DM framework bug, we need this patch to workarund it.
Change-Id: I18ee427fe2457ae42e5c6d1dab3e365fe87e06e4 Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
show more ...
|
| #
6cb8d50f |
| 10-Oct-2018 |
Joseph Chen <chenjh@rock-chips.com> |
arm: bootm-fdt: improve bi_dram[] print format
print start and end address is more easily for users to understand.
Change-Id: I42bcf5aaa0ea7ce4b988336069649e96117f13dd Signed-off-by: Joseph Chen <c
arm: bootm-fdt: improve bi_dram[] print format
print start and end address is more easily for users to understand.
Change-Id: I42bcf5aaa0ea7ce4b988336069649e96117f13dd Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
show more ...
|
| #
e09b1e4a |
| 01-Jun-2018 |
Joseph Chen <chenjh@rock-chips.com> |
bootm-fdt: fixup rk3288w compatible in fdt
1. recoganize RK3288w according to HDMI Revision ID; 2. proive a weak board_fdt_fixup() as common fixup place; 3. move rockchip_display_fixup() into board_
bootm-fdt: fixup rk3288w compatible in fdt
1. recoganize RK3288w according to HDMI Revision ID; 2. proive a weak board_fdt_fixup() as common fixup place; 3. move rockchip_display_fixup() into board_fdt_fixup();
Change-Id: Ib3f4e991ffd7420a8f39390ae067340a65183a26 Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
show more ...
|
| #
9fcf9622 |
| 06-Mar-2018 |
Kever Yang <kever.yang@rock-chips.com> |
rockchip: bootm: update fdt addr for display fixup
fdt has been relocate, can not use the addr from gd.
Change-Id: I108eb13cb62b387f688e6fa1e7d26b2649f67a82 Signed-off-by: Kever Yang <kever.yang@ro
rockchip: bootm: update fdt addr for display fixup
fdt has been relocate, can not use the addr from gd.
Change-Id: I108eb13cb62b387f688e6fa1e7d26b2649f67a82 Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
show more ...
|
| #
419dcb5b |
| 01-Mar-2018 |
Kever Yang <kever.yang@rock-chips.com> |
rockchip: move display dtb fixup to bootm
Change-Id: I25102790fa6330c7b3ce3f9904e250944083c5ca Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
|
| #
9cd0e7c2 |
| 11-Feb-2018 |
Kever Yang <kever.yang@rock-chips.com> |
bootm-fdt: fix compile warning
Change-Id: I5915dc22285e133d52159d6d3ab8cb631f7dfab1 Signed-off-by: Kever Yang <kever.yang@rock-chips.com>
|
| #
0291804a |
| 09-Feb-2018 |
Joseph Chen <chenjh@rock-chips.com> |
bootm-fdt: fix compile warning
Change-Id: Idc1af16d966d19921cf19c233bab0cd35337e8ae Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
|
| #
55fe151c |
| 06-Feb-2018 |
Joseph Chen <chenjh@rock-chips.com> |
bootm-fdt: printf memory bank information
Change-Id: I8630ad245a301d7c1d31ce85a7b67f511cc23fd3 Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
|
| #
ce176305 |
| 23-Nov-2017 |
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com> |
UPSTREAM: arm: Add support of updating dts before fix-up
"ethernet" node fix-up for device tree happens before Linux boot.
There can be requirement of updating "ethernet" node even before fix-up. S
UPSTREAM: arm: Add support of updating dts before fix-up
"ethernet" node fix-up for device tree happens before Linux boot.
There can be requirement of updating "ethernet" node even before fix-up. So, add support of updating "ethernet" node.
Change-Id: I5fcde8776f7f0f5c7323b1340c69d346c9c01833 Signed-off-by: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com> Reviewed-by: York Sun <york.sun@nxp.com> Signed-off-by: Kever Yang <kever.yang@rock-chips.com> (cherry picked from commit 6bedf44714a145e09fddb8c5a03ada210b812ec9)
show more ...
|
| #
984a3c87 |
| 18-Apr-2017 |
B, Ravi <ravibabu@ti.com> |
spl: fdt: support for fdt fixup for falcon boot
Adding support for fdt fixup to update the memory node in device tree for falcon boot.
This is needed for single stage or falcon bootmode, to pass me
spl: fdt: support for fdt fixup for falcon boot
Adding support for fdt fixup to update the memory node in device tree for falcon boot.
This is needed for single stage or falcon bootmode, to pass memory configuration to kernel through DT memory node.
Signed-off-by: Ravi Babu <ravibabu@ti.com> Reviewed-by: Lukasz Majewski <lukma@denx.de>
show more ...
|
| #
0675f992 |
| 19-Jan-2017 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-fsl-qoriq
|
| #
daa92644 |
| 16-Jan-2017 |
Hou Zhiqiang <Zhiqiang.Hou@nxp.com> |
ARMv8/sec_firmware: relocated and renamed the config FSL_PPA_ARMV8_PSCI
Moved the config FSL_PPA_ARMV8_PSCI from fsl-layerscape's Kconfig to Kconfig under armv8 and renamed it to SEC_FIRMWARE_ARMV8_
ARMv8/sec_firmware: relocated and renamed the config FSL_PPA_ARMV8_PSCI
Moved the config FSL_PPA_ARMV8_PSCI from fsl-layerscape's Kconfig to Kconfig under armv8 and renamed it to SEC_FIRMWARE_ARMV8_PSCI.
Signed-off-by: Hou Zhiqiang <Zhiqiang.Hou@nxp.com> Reviewed-by: York Sun <york.sun@nxp.com>
show more ...
|
| #
b5178a1f |
| 16-Dec-2016 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-fsl-qoriq
|
| #
9a561753 |
| 08-Dec-2016 |
macro.wave.z@gmail.com <macro.wave.z@gmail.com> |
ARMv8: Setup PSCI memory and device tree
Newly add ARMv8 PSCI needs to be initialized, be copied or reserved in right place, this patch does all the setup steps.
Signed-off-by: Hongbo Zhang <hongbo
ARMv8: Setup PSCI memory and device tree
Newly add ARMv8 PSCI needs to be initialized, be copied or reserved in right place, this patch does all the setup steps.
Signed-off-by: Hongbo Zhang <hongbo.zhang@nxp.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: York Sun <york.sun@nxp.com>
show more ...
|
| #
2d16a1a6 |
| 08-Dec-2016 |
macro.wave.z@gmail.com <macro.wave.z@gmail.com> |
ARMv8: LS1043A: change macro CONFIG_ARMV8_PSCI definition
NXP/Freescale uses macro CONFIG_ARMV8_PSCI to enable their private PSCI implementation in PPA firmware, but this macro naming too generic, s
ARMv8: LS1043A: change macro CONFIG_ARMV8_PSCI definition
NXP/Freescale uses macro CONFIG_ARMV8_PSCI to enable their private PSCI implementation in PPA firmware, but this macro naming too generic, so this patch replaces it with a specic one CONFIG_FSL_PPA_ARMV8_PSCI. And this macro CONFIG_ARMV8_PSCI will be used for a generic PSCI for ARMv8 which will be added in following patchs.
Signed-off-by: Hongbo Zhang <hongbo.zhang@nxp.com> Reviewed-by: Tom Rini <trini@konsulko.com> Reviewed-by: York Sun <york.sun@nxp.com>
show more ...
|
| #
73eed452 |
| 04-Dec-2016 |
Tom Rini <trini@konsulko.com> |
Merge branch 'master' of git://www.denx.de/git/u-boot-dm
|
| #
63c09417 |
| 26-Nov-2016 |
Masahiro Yamada <yamada.masahiro@socionext.com> |
libfdt: replace ARCH_FIXUP_FDT with ARCH_FIXUP_FDT_MEMORY
Commit e2f88dfd2d96 ("libfdt: Introduce new ARCH_FIXUP_FDT option") allows us to skip memory setup of DTB, but a problem for ARM is that spi
libfdt: replace ARCH_FIXUP_FDT with ARCH_FIXUP_FDT_MEMORY
Commit e2f88dfd2d96 ("libfdt: Introduce new ARCH_FIXUP_FDT option") allows us to skip memory setup of DTB, but a problem for ARM is that spin_table_update_dt() and psci_update_dt() are skipped as well if CONFIG_ARCH_FIXUP_FDT is disabled.
This commit allows us to skip only fdt_fixup_memory_banks() instead of the whole of arch_fixup_fdt(). It will be useful when we want to use a memory node from a kernel DTB as is, but need some fixups for Spin-Table/PSCI.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com> Acked-by: Alexey Brodkin <abrodkin@synopsys.com> Acked-by: Simon Glass <sjg@chromium.org> Fixed build error for x86: Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
e2f88dfd |
| 28-Jul-2016 |
Michal Simek <michal.simek@xilinx.com> |
libfdt: Introduce new ARCH_FIXUP_FDT option
Add new Kconfig option to disable arch_fixup_fdt() calls for cases where U-Boot shouldn't update memory setup in DTB file. One example of usage of this op
libfdt: Introduce new ARCH_FIXUP_FDT option
Add new Kconfig option to disable arch_fixup_fdt() calls for cases where U-Boot shouldn't update memory setup in DTB file. One example of usage of this option is to boot OS with different memory setup than U-Boot use.
Signed-off-by: Michal Simek <michal.simek@xilinx.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
66669fcf |
| 19-Jul-2016 |
Tom Rini <trini@konsulko.com> |
Merge git://git.denx.de/u-boot-fsl-qoriq
Signed-off-by: Tom Rini <trini@konsulko.com>
Conflicts: arch/arm/cpu/armv8/Makefile arch/arm/lib/bootm-fdt.c
|
| #
45684ae3 |
| 28-Jun-2016 |
Hou Zhiqiang <Zhiqiang.Hou@nxp.com> |
ARMv8/PSCI: Fixup the device tree for PSCI
Set the enable-method in the cpu node to PSCI, and create device node for PSCI, when PSCI was enabled.
Signed-off-by: Hou Zhiqiang <Zhiqiang.Hou@nxp.com>
ARMv8/PSCI: Fixup the device tree for PSCI
Set the enable-method in the cpu node to PSCI, and create device node for PSCI, when PSCI was enabled.
Signed-off-by: Hou Zhiqiang <Zhiqiang.Hou@nxp.com> Reviewed-by: York Sun <york.sun@nxp.com>
show more ...
|
| #
6b6024ea |
| 27-Jun-2016 |
Masahiro Yamada <yamada.masahiro@socionext.com> |
arm64: add better and more generic spin-table support
There are two enable methods supported by ARM64 Linux; psci and spin-table. The latter is simpler and helpful for quick SoC bring up. My main
arm64: add better and more generic spin-table support
There are two enable methods supported by ARM64 Linux; psci and spin-table. The latter is simpler and helpful for quick SoC bring up. My main motivation for this patch is to improve the spin-table support, which allows us to boot an ARMv8 system without the ARM Trusted Firmware.
Currently, we have multi-entry code in arch/arm/cpu/armv8/start.S and the spin-table is supported in a really ad-hoc way, and I see some problems:
- We must hard-code CPU_RELEASE_ADDR so that it matches the "cpu-release-addr" property in the DT that comes from the kernel tree.
- The Documentation/arm64/booting.txt in Linux requires that the release address must be zero-initialized, but it is not cared by the common code in U-Boot. We must do it in a board function.
- There is no systematic way to protect the spin-table code from the kernel. We are supposed to do it in a board specific manner, but it is difficult to predict where the spin-table code will be located after the relocation. So, it also makes difficult to hard-code /memreserve/ in the DT of the kernel.
So, here is a patch to solve those problems; the DT is run-time modified to reserve the spin-table code (+ cpu-release-addr). Also, the "cpu-release-addr" property is set to an appropriate address after the relocation, which means we no longer need the hard-coded CPU_RELEASE_ADDR.
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
show more ...
|