google/eve: Fix DRAM DQS map

This change fixes the two sets of pins that were swapped in the
map of DQS signals from CPU to DRAM for channel 1.

Although this does not appear to have any impact to the system it
does result in different register values for DQS pin mapping that
are programmed inside FSP.

BUG=chrome-os-partner:58666
TEST=This fix was verified against the current schematic and using
FSP debug output.

Change-Id: I45b821071ba287493b3b13204b7f5b38e06eee75
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://review.coreboot.org/18279
Tested-by: build bot (Jenkins)
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
This commit is contained in:
Duncan Laurie 2017-02-01 16:37:29 -08:00 committed by Martin Roth
parent 561bebfbaa
commit 9471d00a4f
1 changed files with 1 additions and 1 deletions

View File

@ -32,7 +32,7 @@ void mainboard_memory_init_params(FSPM_UPD *mupd)
/* DQS CPU<>DRAM map */
const u8 dqs_map[2][8] = {
{ 1, 0, 2, 3, 4, 5, 6, 7 },
{ 1, 0, 4, 5, 3, 2, 7, 6 } };
{ 1, 0, 5, 4, 2, 3, 7, 6 } };
/* Rcomp resistor */
const u16 rcomp_resistor[] = { 200, 81, 162 };
/* Rcomp target */