78f4e2fea0
If OPAL_RTC_READ is busy and does not return the information on the first run, as returning OPAL_BUSY_EVENT, the system will crash since ymd and hmsm variable will contain junk values. This is happening because we were not calling OPAL_RTC_READ again after OPAL_POLL_EVENTS' return, which would finally replace the old/junk hmsm and ymd values. The code was also mixing OPAL_RTC_READ and OPAL_POLL_EVENTS return values. This patch fix this logic and guarantee that we call OPAL_RTC_READ after OPAL_POLL_EVENTS return, and guarantee the code will only proceed if OPAL_RTC_READ returns OPAL_SUCCESS. Reviewed by: jhibbits Approved by: jhibbits (mentor) Differential Revision: https://reviews.freebsd.org/D16617 |
||
---|---|---|
.. | ||
opal_console.c | ||
opal_dev.c | ||
opal_i2c.c | ||
opal_i2cm.c | ||
opal_pci.c | ||
opal_sensor.c | ||
opal.c | ||
opal.h | ||
opalcall.S | ||
platform_powernv.c | ||
powernv_centaur.c | ||
powernv_xscom.c |