Since OPAL_GET_MSG does not discriminate between message types, asynchronous completion events may be received in the OPAL_GET_MSG call, which dequeues them from the list, thus preventing OPAL_CHECK_ASYNC_COMPLETION from succeeding. Handle this case by integrating with the messaging framework. |
||
---|---|---|
.. | ||
opal_async.c | ||
opal_console.c | ||
opal_dev.c | ||
opal_flash.c | ||
opal_hmi.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 | ||
xive.c |