Skip to content

mvebu: ddr3: Armada-385 read ODT configuration

Chris Packham u-boot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2mv_ddr: ddr3: Use correct bitmask for read sample delaydrivers/ddr/marvell/a38x/ddr3_training_hw_algo.c+1 -11 reply
2/2mv_ddr: ddr3: Update {min,max}_read_sample calculationdrivers/ddr/marvell/a38x/ddr3_training_hw_algo.c+2 -22 replies

Reviews trailers per patch

All 2 patches have a Reviewed-by or Acked-by.

PatchBaruch SiachStefan Roese
1/2R-b
2/2T-b R-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH 0/2] mvebu: ddr3: Armada-385 read ODT configuration

We've been doing some finer grained testing on our Armada-385 based platforms and found that on a read the ODT was kicking in 3 clock cycles too early.

It is likely this has gone unnoticed because prior to commit 247c80d6b8ad ("mv_ddr: ddr3: only use active chip-selects when tuning ODT") most systems would have ended up maxing out the read ODT values.

Marvell have been directing us to add 3 to the min/max read calculation and that seems to do the trick. Rather than just adding +3 I've adjusted the existing manipulations.

I've only got access to our x530 platform at the moment so it would be good if anyone with access to other Armada-385 could take this for a spin.

Chris Packham (2):
mv_ddr: ddr3: Use correct bitmask for read sample delay
mv_ddr: ddr3: Update {min,max}_read_sample calculation

 drivers/ddr/marvell/a38x/ddr3_training_hw_algo.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
Signature · 1 line
2.25.1