Change DBG macro to prlog calls for platforms/ibm-fsp/lxvpd.c

No functional changes, when running with higher log level, you'll
get debug messages without recompiling!

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Change DBG to prlog PR_TRACE and PR_INSANE in hw/fsp/fsp-sensor.c

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
use prlog(PR_INSANE in hw/fsp/fsp.c in place of DBG ifdef

This means that when log level of PR_INSANE is enabled, you will
get traces of messages to/from FSP.

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Use prlog rather than DBG #ifdef in hw/fsp/fsp-leds.c

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Use prlog instead of DBG macros in hw/fsp/fsp-rtc.c

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Remove (unused) DBG macros from hw/fsp/fsp-nvram.c

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Convert hw/slw.c from DBG #define to prlog

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Convert hw/fsi-master.c from DBG define to prlog PR_INSANE

All the DBG() macros seemed to be more trace oriented than debug.

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
Use prlog(PR_INSANE in hw/chiptod.c instead of DBG macro.

It seems like these are more of things to trace rather than too useful
for random debugging... I could be wrong, but that's why you're reading
this, reviewing this code. RIGHT!!??!?

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
hw/fake-rtc.c now uses prlog(PR_TRACE instead of DBG macro

Only two possible printouts, so probably fine for debug level.

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
remove unused DBG and FSP_TRACE macros from hw/psi.c

Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>