From: "Marek Behún" <kabel@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: u-boot@lists.denx.de
Subject: Re: [PATCH u-boot-mvebu 10/10] arm: mvebu: turris_omnia: Support old DDR3 training, selectable via env var
Date: Wed, 15 May 2024 10:59:06 +0200 [thread overview]
Message-ID: <20240515105906.3cfca4fb@dellmb> (raw)
In-Reply-To: <149e251a-baa7-4512-990a-d332d0d6177f@denx.de>
On Mon, 6 May 2024 12:03:55 +0200
Stefan Roese <sr@denx.de> wrote:
> Hi Marek,
>
> On 4/15/24 18:30, Marek Behún wrote:
> > Support old DDR3 training code on Turris Omnia, selectable by U-Boot
> > enviroment variable.
> >
> > Users experiencing DDR3 initialization failures or random crashes of the
> > operating system due to incorrect DDR3 configuration can select the old
> > DDR3 training implementation to fix those issues by setting the
> > environment variable
> > env set omnia_ddr3_training old
> > env save
> >
> > Signed-off-by: Marek Behún <kabel@kernel.org>
> > ---
> > arch/arm/mach-mvebu/Kconfig | 1 +
> > board/CZ.NIC/turris_omnia/Makefile | 1 +
> > board/CZ.NIC/turris_omnia/old_ddr3_training.c | 79 +++++++++++++++++++
> > board/CZ.NIC/turris_omnia/turris_omnia.c | 2 +-
> > 4 files changed, 82 insertions(+), 1 deletion(-)
> > create mode 100644 board/CZ.NIC/turris_omnia/old_ddr3_training.c
>
> For turris_omnia_defconfig, this is dropped when compiled:
>
> drivers/ddr/marvell/a38x/old/ddr3_debug.c:776:12: warning:
> 'ddr3_tip_access_atr' declared 'static' but never defined
> [-Wunused-function]
> 776 | static int ddr3_tip_access_atr(u32 dev_num, u32 flag_id, u32
> value, u32 **ptr);
> | ^~~~~~~~~~~~~~~~~~~
And it also seems that there is still something wrong with this
old DDR training code port. Some boards still experience random bugs
with this, but not with the U-Boot from 2015. :-(
next prev parent reply other threads:[~2024-05-15 8:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 16:30 [PATCH u-boot-mvebu 00/10] Turris Omnia DDR training changes Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 01/10] ddr: marvell: a38x: debug: return from ddr3_tip_print_log() early if we won't print anything Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 02/10] ddr: marvell: a38x: debug: Remove unused variables Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 03/10] ddr: marvell: a38x: debug: Define DDR_VIEWER_TOOL variables only if needed, and make them static Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 04/10] ddr: marvell: a38x: debug: Allow compiling with immutable debug settings to reduce binary size Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 05/10] arm: mvebu: turris_omnia: Enable immutable debug settings in DDR3 training by default Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 06/10] ddr: marvell: a38x: Import old DDR training code from 2017 version of U-Boot Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 07/10] ddr: marvell: a38x: old: Fix some compiler warning of the old code Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 08/10] ddr: marvell: a38x: old: Backport immutable debug settings Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 09/10] arm: mvebu: a38x: Add optional support for using old DDR3 training code Marek Behún
2024-04-15 16:30 ` [PATCH u-boot-mvebu 10/10] arm: mvebu: turris_omnia: Support old DDR3 training, selectable via env var Marek Behún
2024-05-06 10:03 ` Stefan Roese
2024-05-15 8:59 ` Marek Behún [this message]
2024-05-15 9:10 ` Stefan Roese
2024-05-15 9:24 ` Marek Behún
2024-05-15 15:11 ` Stefan Roese
2024-04-15 22:20 ` [PATCH u-boot-mvebu 00/10] Turris Omnia DDR training changes Tony Dinh
2024-04-16 10:10 ` Marek Behún
2024-04-16 19:45 ` Tony Dinh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240515105906.3cfca4fb@dellmb \
--to=kabel@kernel.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox