UPSTREAM: mainboard/google/reef: reverse the memory config bits
I mistakenly assumed the order of the bits matched how one would assign values as they wrote them msb .. lsb. However, the gpio lib doesn't do that. Correct the order so that values are read out correctly. BUG=chrome-os-partner:54949t BRANCH=None TEST=None Signed-off-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/15753 Reviewed-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-by: Furquan Shaikh <furquan@google.com> Tested-by: build bot (Jenkins) Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Change-Id: I5304dfe2ba6f8eb073acab3377327167573ec2cc Reviewed-on: https://chromium-review.googlesource.com/362344 Commit-Ready: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Reviewed-by: Furquan Shaikh <furquan@chromium.org>
This commit is contained in:
parent
132351dbb6
commit
da016515f6
1 changed files with 4 additions and 1 deletions
|
|
@ -112,7 +112,10 @@ static const struct lpddr4_cfg lp4cfg = {
|
|||
void mainboard_memory_init_params(struct FSPM_UPD *memupd)
|
||||
{
|
||||
int mem_sku;
|
||||
gpio_t pads[] = { MEM_CONFIG3, MEM_CONFIG2, MEM_CONFIG1, MEM_CONFIG0 };
|
||||
gpio_t pads[] = {
|
||||
[3] = MEM_CONFIG3, [2] = MEM_CONFIG2,
|
||||
[1] = MEM_CONFIG1, [0] = MEM_CONFIG0,
|
||||
};
|
||||
|
||||
/*
|
||||
* Read memory SKU id with internal pullups enabled to handle
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue