aboutsummaryrefslogtreecommitdiffstats
path: root/board_enable.c
diff options
context:
space:
mode:
authorEdward O'Callaghan <quasisec@google.com>2020-07-31 12:21:02 +1000
committerEdward O'Callaghan <quasisec@chromium.org>2020-12-16 10:29:41 +0000
commit855d6b6f11e220b94c8d10059110f37797933a3e (patch)
treebc4f7953b78fa83ebaa30de55e45ffaf9dae5d57 /board_enable.c
parent9f90f4c01b6b22aa425e8e8abc34ef76b422c507 (diff)
downloadflashrom-855d6b6f11e220b94c8d10059110f37797933a3e.tar.gz
flashrom-855d6b6f11e220b94c8d10059110f37797933a3e.tar.bz2
flashrom-855d6b6f11e220b94c8d10059110f37797933a3e.zip
sb600spi.c: Add support for 0x790b rev 0x61 (AMD Zen)
Adds support for rev 0x59 || 0x61 of did 0x790b. This is quite confusing however it turns out FCH chipsets called 'Promontory' contain the so-called SPI100 ip core that uses memory mapping and not a ring buffer for transactions. Typically this is found on both Stoney Ridge and Zen platforms. In light of this, separate out the promontory path into its own callback struct state tracker so that it's implementation does not interfere with previous generations that predate the SPI100 controller. Since there is some life-time state required to track the mapping during between the first attempted read and the final tear-down of the spi master we take the opportunity to avoid static locals and instead implement the functionality in a re-entrant way for follow up clean ups. BUG=none BRANCH=none TEST= Zork => 'Promontory (rev 0x61) detected.' && Grunt => 'Promontory (rev 0x4b) detected.' Change-Id: I5ce63b5de863aed0442cb4ffeff981e9b2fa445b Signed-off-by: Edward O'Callaghan <quasisec@google.com> Reviewed-on: https://review.coreboot.org/c/flashrom/+/44073 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Sam McNally <sammc@google.com>
Diffstat (limited to 'board_enable.c')
0 files changed, 0 insertions, 0 deletions