From: Marek Behun <marek.behun@nic.cz>
To: u-boot@lists.denx.de
Subject: [PATCH u-boot-marvell 00/18] Upgrade A38x DDR3 training to version 14.0.0
Date: Tue, 9 Feb 2021 15:57:38 +0100 [thread overview]
Message-ID: <20210209155738.7cabb96b@nic.cz> (raw)
In-Reply-To: <1d4156d3-5517-d0eb-dcdf-05421622e5e3@alliedtelesis.co.nz>
On Tue, 9 Feb 2021 06:50:35 +0000
Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
> On 9/02/21 3:07 pm, Marek Behun wrote:
> > On Tue, 9 Feb 2021 01:08:54 +0000
> > Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
> >
> >> On 9/02/21 1:16 pm, Chris Packham wrote:
> >>> On 9/02/21 9:18 am, Marek Behun wrote:
> >>>> On Mon, 8 Feb 2021 20:11:06 +0000
> >>>> Chris Packham <Chris.Packham@alliedtelesis.co.nz> wrote:
> >>>>
> >>>>> Hi Marek,
> >>>>>
> >>>>> Do you have this in a repo I can pull from? I've got a couple of boards
> >>>>> I can give this a spin on.
> >>>> https://gitlab.nic.cz/turris/turris-omnia-uboot/
> >>>> branch v2021.04-rc-mv-ddr-14.0.0
> >>>>
> >>>> also please test branch v2021.04-rc-mv-ddr-14.0.0-samsung-ddr-fix, that
> >>>> one contains one more commit that is needed for Omnia with Samsung DDR
> >>>> chips.
> >>> I've tested the dm-88f6820-amc board. Training completed without
> >>> issue, as does memtester running from Linux.
> >>>
> >>> Hit a bit of a snag on the x530 because the changes pushed it over the
> >>> SPL size (it was already pretty close). I'll look to see if there's
> >>> anything I can drop out or maybe bump the SPL size (I never did get a
> >>> clear answer from Marvell as to what the size limit actually is).
> >> I can temporarily work around the size issue by disabling watchdog
> >> support in SPL (I really don't want that to be the long term solution).
> >>
> >> But then I encounter an odd problem. When I "reset" the board gets
> >> through the DDR training but never makes it to u-boot proper, but if I
> >> power cycle it boots through to the u-boot prompt. This doesn't happen
> >> on the db-88f6820-amc board. One difference between the x530 and the amc
> >> board is that the x530 has ECC so maybe something is going into the
> >> weeds if ECC has already been enabled by a previous boot.
> >>
> > Could you bisect which commit causes this?
> Seems to be the last one (ddr: marvell: a38x: fix SPLIT_OUT_MIX state
> decision) not entirely sure what the problem is. So I guess you can
> consider the upstream update good, the fix SPLIT_OUT_MIX not so much it
> happens to be the thing that causes the issue and the straw that tips
> the build size over the limit.
BTW Chris if the first 18 patches are working for your devices, could
you please give Tested-by? Thanks.
Marek
next prev parent reply other threads:[~2021-02-09 14:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 18:34 [PATCH u-boot-marvell 00/18] Upgrade A38x DDR3 training to version 14.0.0 Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 01/18] ddr: marvell: a38x: fix write leveling suplementary algo Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 02/18] ddr: marvell: a38x: import header change from upstream Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 03/18] ddr: marvell: a38x: add ddr32 support Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 04/18] ddr: marvell: a38x: add ddr 32bit ECC support Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 05/18] ddr: marvell: a38x: import header change from upstream Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 06/18] ddr: marvell: a38x: fix 32bit Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 07/18] ddr: marvell: a38x: fix memory size calculation using 32bit bus width Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 08/18] ddr: marvell: a38x: import header change from upstream Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 09/18] ddr: marvell: a38x: allow board specific ODT configuration Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 10/18] ddr: marvell: a38x: add 16Gbit memory devices support Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 11/18] ddr: marvell: a38x: add support for twin-die combined memory device Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 12/18] ddr: marvell: a38x: disable WL phase correction stage in case of bus_width=16bit Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 13/18] ddr: marvell: a38x: import header change from upstream Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 14/18] ddr: marvell: a38x: fix memory cs size function Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 15/18] ddr: marvell: a38x: import code change from upstream Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 16/18] ddr: marvell: a38x: enum mv_ddr_twin_die: change order Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 17/18] ddr: marvell: a38x: bump version to 14.0.0 Marek Behún
2021-02-08 18:34 ` [PATCH u-boot-marvell 18/18] ddr: marvell: a38x: fix comment in conditional macro Marek Behún
2021-02-08 18:51 ` [PATCH u-boot-marvell 00/18] Upgrade A38x DDR3 training to version 14.0.0 Marek Behun
2021-02-08 20:11 ` Chris Packham
2021-02-08 20:18 ` Marek Behun
2021-02-09 0:16 ` Chris Packham
2021-02-09 1:08 ` Chris Packham
2021-02-09 2:07 ` Marek Behun
2021-02-09 2:15 ` Chris Packham
2021-02-09 6:50 ` Chris Packham
2021-02-09 13:15 ` Marek Behun
2021-02-09 21:54 ` Chris Packham
2021-02-09 14:57 ` Marek Behun [this message]
2021-02-09 9:15 ` Pali Rohár
2021-02-09 20:30 ` Chris Packham
2021-02-08 22:07 ` Marek Behun
2021-02-09 21:57 ` Chris Packham
2021-02-18 19:56 ` Marek Behun
2021-02-19 7:38 ` Stefan Roese
2021-02-19 16:13 ` Marek Behún
2021-02-19 16:37 ` Stefan Roese
2021-02-24 14:28 ` Pavol Rohár
2021-02-25 12:57 ` 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=20210209155738.7cabb96b@nic.cz \
--to=marek.behun@nic.cz \
--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