From d1eba2e2cc7577617c7123c7507cffeed511e3c5 Mon Sep 17 00:00:00 2001 From: Krystian Hebel Date: Fri, 29 Oct 2021 12:57:39 +0200 Subject: [PATCH] soc/power9/romstage.c: don't check for exact match for SCOM test This was previously hardcoded to our CPU version and wouldn't work for any other CPU models. Signed-off-by: Krystian Hebel Change-Id: I6f537ff225387a29d5d609c05729e1ab993fbd37 --- src/soc/ibm/power9/romstage.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/soc/ibm/power9/romstage.c b/src/soc/ibm/power9/romstage.c index 0f1ca30623e..8fe9ff580f0 100644 --- a/src/soc/ibm/power9/romstage.c +++ b/src/soc/ibm/power9/romstage.c @@ -378,13 +378,13 @@ void main(void) timestamp_add_now(TS_AFTER_INITRAM); /* Test if SCOM still works. Maybe should check also indirect access? */ - printk(BIOS_DEBUG, "0xF000F = %llx\n", read_scom(0xf000f)); + printk(BIOS_DEBUG, "0xF000F = %llx\n", read_scom(0xF000F)); /* * Halt to give a chance to inspect FIRs, otherwise checkstops from * ramstage may cover up the failure in romstage. */ - if (read_scom(0xf000f) != 0x223d104900008040) + if (read_scom(0xF000F) == 0xFFFFFFFFFFFFFFFF) die("SCOM stopped working, check FIRs, halting now\n"); cbmem_initialize_empty();