diff options
author | Aaron Durbin <adurbin@chromium.org> | 2018-08-07 12:30:53 -0600 |
---|---|---|
committer | Aaron Durbin <adurbin@chromium.org> | 2018-08-09 16:56:57 +0000 |
commit | 042b53ad65da38caed1584e0547afbf2e78b6fe0 (patch) | |
tree | 57e4dbccc836230323a09ce2d60c757188a21c74 /src/soc/marvell/mvmap2315/cbmem.c | |
parent | bb7424f30c3b7b8938326f75123b39c0ba4c4027 (diff) |
mb/google/octopus: add support for fetching DRAM part number from CBI
Add 3 new Kconfig options:
DRAM_PART_NUM_IN_CBI
DRAM_PART_NUM_ALWAYS_IN_CBI
DRAM_PART_IN_CBI_BOARD_ID_MIN
These control whether to 1. attempt to use CBI at all 2. always use cbi
and 3. conditionally use cbi based on board id. The intent is that the
MIN variant would be used for the tranisition period then cut over to
ALWAYS after full transition. Since multiple OEMs have different
schedules these options are there to bridge the gap. yorp. bip, and
octopus build targets would never flip DRAM_PART_NUM_IN_CBI, but in case
someone does the MIN values are 255 to always take the old path.
BUG=b:112203105
TEST=Set correct part number on phaser during testing.
Change-Id: If9a0102806d78e89330b42aa6947d503a8a2deac
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://review.coreboot.org/27946
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Furquan Shaikh <furquan@google.com>
Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net>
Diffstat (limited to 'src/soc/marvell/mvmap2315/cbmem.c')
0 files changed, 0 insertions, 0 deletions