UPSTREAM: mainboard/google/poppy: Update DQS and DQ Byte mappings for poppy

poppy schematics have undergone change after review, update
DQS and DQ Byte mappings based on the new schematics.

BUG=chrome-os-partner:61856
BRANCH=None
TEST= Build and boot all the poppy proto SKUs to OS.

Change-Id: I80eab8bc6fb486bab959ab308c93d1d3031247bc
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id: b4a159706e
Original-Change-Id: Ie4532035f37c25540abb26122234f6e3346ede69
Original-Signed-off-by: Rizwan Qureshi <rizwan.qureshi@intel.com>
Original-Signed-off-by: Furquan Shaikh <furquan@chromium.org>
Original-Reviewed-on: https://review.coreboot.org/18133
Original-Reviewed-by: Furquan Shaikh <furquan@google.com>
Original-Tested-by: build bot (Jenkins)
Original-Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Reviewed-on: https://chromium-review.googlesource.com/430171
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
This commit is contained in:
Rizwan Qureshi 2017-01-13 12:45:19 +05:30 committed by chrome-bot
commit eac7b9e19b

View file

@ -25,14 +25,14 @@ void mainboard_memory_init_params(FSPM_UPD *mupd)
FSP_M_CONFIG *mem_cfg = &mupd->FspmConfig;
/* DQ byte map */
const u8 dq_map[2][12] = {
{ 0xF0, 0x0F, 0x00, 0xF0, 0x0F, 0xF0,
{ 0x0F, 0xF0, 0x00, 0xF0, 0x0F, 0xF0,
0x0F, 0x00, 0xFF, 0x00, 0xFF, 0x00 },
{ 0x33, 0xCC, 0x00, 0x33, 0xCC, 0x33,
{ 0xCC, 0x33, 0x00, 0x33, 0xCC, 0x33,
0xCC, 0x00, 0xFF, 0x00, 0xFF, 0x00 }
};
/* DQS CPU<>DRAM map */
const u8 dqs_map[2][8] = {
{ 0, 3, 1, 2, 4, 7, 6, 5 },
{ 2, 3, 1, 0, 4, 7, 6, 5 },
{ 5, 6, 0, 3, 4, 7, 2, 1 },
};
/* Rcomp resistor */