All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Behún" <kabel@kernel.org>
To: Stefan Roese <sr@denx.de>
Cc: "Chris Packham" <judge.packham@gmail.com>,
	"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	"Mario Six" <mario.six@gdsys.cc>,
	"Dennis Gilmore" <dgilmore@redhat.com>,
	"Marek Behún" <marek.behun@nic.cz>
Subject: Re: [PATCH u-boot-marvell RFC] PLEASE TEST: ddr: marvell: a38x: fix BYTE_HOMOGENEOUS_SPLIT_OUT decision
Date: Wed, 16 Feb 2022 14:26:58 +0100	[thread overview]
Message-ID: <20220216142658.428ffc89@dellmb> (raw)
In-Reply-To: <2b25f4a4-aca1-a4cd-283b-7d8f5f63c4d1@denx.de>

On Wed, 16 Feb 2022 09:41:44 +0100
Stefan Roese <sr@denx.de> wrote:

> On 2/15/22 23:21, Chris Packham wrote:
> > On Fri, Feb 11, 2022 at 5:25 AM Marek Behún <kabel@kernel.org> wrote:  
> >>
> >> From: Marek Behún <marek.behun@nic.cz>
> >>
> >> In commit 3fc92a215b69 ("ddr: marvell: a38x: fix SPLIT_OUT_MIX state
> >> decision") I ported a cleaned up and changed version of patch
> >>    mv_ddr: a380: fix SPLIT_OUT_MIX state decision
> >>
> >> In the port we removed checking for BYTE_HOMOGENEOUS_SPLIT_OUT bit,
> >> because:
> >> - the fix seemed to work without it
> >> - the bit was checked for only at one place out of two, while the second
> >>    bit, BYTE_SPLIT_OUT_MIX, was checked for in both cases
> >> - without the removal it didn't work on Allied Telesis' x530 board
> >>
> >> We recently had a chance to test on more boards, and it seems that the
> >> change needs to be opposite: instead of removing the check for
> >> BYTE_HOMOGENEOUS_SPLIT_OUT from the first if() statement, the check
> >> needs to be added also to the second one - it needs to be at both
> >> places.
> >>
> >> With this change all the Turris Omnia boards I have had available to
> >> test seem to work, I didn't encounter not even one failed DDR training.
> >>
> >> As last time, I am noting that I do not understand what this code is
> >> actually doing, I haven't studied the DDR training algorithm and
> >> I suspect that no one will be able to explain it to U-Boot contributors,
> >> so we are left with this blind poking in the code with testing whether
> >> it works on several boards and hoping it doesn't break anything for
> >> anyone :-(.
> >>
> >> Signed-off-by: Marek Behún <marek.behun@nic.cz>  
> > 
> > Tested-by: Chris Packham <judge.packham@gmail.com>  
> 
> Reviewed-by: Stefan Roese <sr@denx.de>

Dear Stefan,

will you apply this (removing the PLEASE TEST: prefix) or should I send
it again without it?

I am going to send another patch which will reset the board immediately
if DDR training fails, so I can send with that one.

Marek

  reply	other threads:[~2022-02-16 13:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 16:25 [PATCH u-boot-marvell RFC] PLEASE TEST: ddr: marvell: a38x: fix BYTE_HOMOGENEOUS_SPLIT_OUT decision Marek Behún
2022-02-15 22:21 ` Chris Packham
2022-02-16  8:41   ` Stefan Roese
2022-02-16 13:26     ` Marek Behún [this message]
2022-02-16 13:41       ` Stefan Roese

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=20220216142658.428ffc89@dellmb \
    --to=kabel@kernel.org \
    --cc=dgilmore@redhat.com \
    --cc=judge.packham@gmail.com \
    --cc=marek.behun@nic.cz \
    --cc=mario.six@gdsys.cc \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.