diff options
| author | Josef Schlehofer <pepe.schlehofer@gmail.com> | 2022-02-17 10:01:29 +0100 |
|---|---|---|
| committer | Christian Lamparter <chunkeey@gmail.com> | 2022-02-20 14:26:42 +0100 |
| commit | 696f0a1cb466d580a91a62717e474bb11e3d4a53 (patch) | |
| tree | df3cc931f264f9e908abe42b73652a8dee953d41 /target/linux/bcm47xx | |
| parent | 82da1dfd69aa80d31cd152b5c7bfb76fb25bb03f (diff) | |
| download | upstream-696f0a1cb466d580a91a62717e474bb11e3d4a53.tar.gz upstream-696f0a1cb466d580a91a62717e474bb11e3d4a53.tar.bz2 upstream-696f0a1cb466d580a91a62717e474bb11e3d4a53.zip | |
uboot-mvebu: backport pending patches for Marvell A38x
100-ddr-marvell-a38x-fix-BYTE_HOMOGENEOUS_SPLIT_OUT-deci.patch [1]:
SoC Marvell A38x is used in Turris Omnia, and we thought that with recent
fiddling around DDR training to fix it once for all, there were
reproduced the issue in the upcoming new revision Turris Omnia boards.
101-arm-mvebu-spl-Add-option-to-reset-the-board-on-DDR-t.patch [2]:
This is useful when some board may occasionally fail with DDR training,
and it adds the option to reset the board on the DDR training failure
102-arm-mvebu-turris_omnia-Reset-the-board-immediately-o.patch [3]:
This enables the option CONFIG_DDR_RESET_ON_TRAINING_FAILURE (added by
101 patch), so the Turris Omnia board is restarted immediately, and it
does not require to reset the board manually or wait 120s for MCU to
reset the board
[1] https://patchwork.ozlabs.org/project/uboot/patch/20220217000837.13003-1-kabel@kernel.org/
[2] https://patchwork.ozlabs.org/project/uboot/patch/20220217000849.13028-1-kabel@kernel.org/
[3] https://patchwork.ozlabs.org/project/uboot/patch/20220217000849.13028-2-kabel@kernel.org/
Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
Diffstat (limited to 'target/linux/bcm47xx')
0 files changed, 0 insertions, 0 deletions