From: Chris Packham <judge.packham@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/1] ARM: mvebu: Armada-38x DDR training update
Date: Mon, 3 Dec 2018 14:26:48 +1300 [thread overview]
Message-ID: <20181203012649.20344-1-judge.packham@gmail.com> (raw)
Hi All,
I had a faulty board to debug at $dayjob. Part of that involved trying the
latest DDR training code from Marvell. That didn't fix by problem (I
suspect a manufacturing issue with that board).
Since I've done the work anyway I figured I'd send this out. Most of the
delta is code movement and tidy up. There's very little behavioural
change for A38X. This may however be useful if/when someone starts
looking at the newer Armada-3700/3900 SoCs.
Changes in v2:
- record sha1 of the commit we're syncing to.
- Highlight some of the fixes that affect a38x
Chris Packham (1):
ARM: mvebu: a38x: sync ddr training code with mv_ddr-armada-18.09.02
board/CZ.NIC/turris_omnia/turris_omnia.c | 4 +-
board/Marvell/db-88f6820-amc/db-88f6820-amc.c | 2 +-
board/Marvell/db-88f6820-gp/db-88f6820-gp.c | 2 +-
board/gdsys/a38x/controlcenterdc.c | 2 +-
board/kobol/helios4/helios4.c | 2 +-
board/solidrun/clearfog/clearfog.c | 2 +-
drivers/ddr/marvell/a38x/ddr3_debug.c | 414 +--------------
drivers/ddr/marvell/a38x/ddr3_init.c | 91 +---
drivers/ddr/marvell/a38x/ddr3_init.h | 43 +-
drivers/ddr/marvell/a38x/ddr3_topology_def.h | 78 ---
drivers/ddr/marvell/a38x/ddr3_training.c | 484 +++++++++---------
drivers/ddr/marvell/a38x/ddr3_training_bist.c | 1 +
.../a38x/ddr3_training_centralization.c | 3 +
drivers/ddr/marvell/a38x/ddr3_training_db.c | 172 ++++---
.../ddr/marvell/a38x/ddr3_training_hw_algo.c | 1 +
drivers/ddr/marvell/a38x/ddr3_training_ip.h | 38 --
.../ddr/marvell/a38x/ddr3_training_ip_def.h | 31 --
.../marvell/a38x/ddr3_training_ip_engine.c | 2 +
.../marvell/a38x/ddr3_training_ip_engine.h | 1 +
.../ddr/marvell/a38x/ddr3_training_ip_flow.h | 91 +---
.../marvell/a38x/ddr3_training_ip_prv_if.h | 10 +-
.../ddr/marvell/a38x/ddr3_training_leveling.c | 75 +--
.../ddr/marvell/a38x/ddr3_training_leveling.h | 1 -
drivers/ddr/marvell/a38x/ddr3_training_pbs.c | 7 +-
drivers/ddr/marvell/a38x/ddr_topology_def.h | 107 +++-
drivers/ddr/marvell/a38x/ddr_training_ip_db.h | 2 -
drivers/ddr/marvell/a38x/dram_if.h | 13 +
.../ddr/marvell/a38x/mv_ddr_build_message.c | 2 +-
drivers/ddr/marvell/a38x/mv_ddr_common.h | 38 +-
drivers/ddr/marvell/a38x/mv_ddr_plat.c | 181 ++++---
drivers/ddr/marvell/a38x/mv_ddr_plat.h | 12 +-
drivers/ddr/marvell/a38x/mv_ddr_regs.h | 19 +
drivers/ddr/marvell/a38x/mv_ddr_spd.c | 16 +-
drivers/ddr/marvell/a38x/mv_ddr_topology.c | 215 ++++++--
drivers/ddr/marvell/a38x/mv_ddr_topology.h | 214 +++++++-
drivers/ddr/marvell/a38x/mv_ddr_training_db.h | 40 ++
drivers/ddr/marvell/a38x/xor.c | 8 +-
37 files changed, 1163 insertions(+), 1261 deletions(-)
delete mode 100644 drivers/ddr/marvell/a38x/ddr3_topology_def.h
create mode 100644 drivers/ddr/marvell/a38x/dram_if.h
create mode 100644 drivers/ddr/marvell/a38x/mv_ddr_training_db.h
--
2.19.2
next reply other threads:[~2018-12-03 1:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 1:26 Chris Packham [this message]
2018-12-03 1:26 ` [U-Boot] [PATCH v2 1/1] ARM: mvebu: a38x: sync ddr training code with mv_ddr-armada-18.09.02 Chris Packham
2018-12-05 6:55 ` Stefan Roese
2018-12-06 10:56 ` Baruch Siach
2018-12-09 10:12 ` 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=20181203012649.20344-1-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--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