aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVasant Hegde <hegdevasant@linux.vnet.ibm.com>2018-09-19 14:01:20 +0530
committerStewart Smith <stewart@linux.ibm.com>2018-09-20 14:30:51 +1000
commit904623dbbda4a7e467814898014a0e8e4eeb1a5f (patch)
tree5e4e7fc2171881c40b3bc029446fe26976e78552
parent832cac15956cc9af32d0196da0dc82e7aeef9e19 (diff)
downloadskiboot-904623dbbda4a7e467814898014a0e8e4eeb1a5f.zip
skiboot-904623dbbda4a7e467814898014a0e8e4eeb1a5f.tar.gz
skiboot-904623dbbda4a7e467814898014a0e8e4eeb1a5f.tar.bz2
FSP: Improve Reset/Reload log message
Below message is confusing. Lets make it clear. FSP sends "R/R complete notification" whenever there is a dump. We use `flag` to identify whether its its R/R completion -OR- just new dump notification. [ 483.406351956,6] FSP: SP says Reset/Reload complete [ 483.406354278,5] DUMP: FipS dump available. ID = 0x1a00001f [size: 6367640 bytes] [ 483.406355968,7] A Reset/Reload was NOT done Signed-off-by: Vasant Hegde <hegdevasant@linux.vnet.ibm.com> Signed-off-by: Stewart Smith <stewart@linux.ibm.com>
-rw-r--r--hw/fsp/fsp.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/hw/fsp/fsp.c b/hw/fsp/fsp.c
index 4beb330..f7e6748 100644
--- a/hw/fsp/fsp.c
+++ b/hw/fsp/fsp.c
@@ -1299,7 +1299,6 @@ static bool fsp_local_command(u32 cmd_sub_mod, struct fsp_msg *msg)
fsp_alloc_inbound(msg);
return true;
case FSP_CMD_SP_RELOAD_COMP:
- prlog(PR_INFO, "FSP: SP says Reset/Reload complete\n");
if (msg->data.bytes[3] & PPC_BIT8(0)) {
fsp_fips_dump_notify(msg->data.words[1],
msg->data.words[2]);
@@ -1309,8 +1308,9 @@ static bool fsp_local_command(u32 cmd_sub_mod, struct fsp_msg *msg)
msg->data.words[3]);
}
if (msg->data.bytes[3] & PPC_BIT8(2)) {
- prlog(PR_DEBUG, " A Reset/Reload was NOT done\n");
+ prlog(PR_INFO, "FSP: SP Reset/Reload was NOT done\n");
} else {
+ prlog(PR_INFO, "FSP: SP says Reset/Reload complete\n");
/* Notify clients that the FSP is back up */
fsp_notify_rr_state(FSP_RELOAD_COMPLETE);
fsp_repost_queued_msgs_post_rr();