xscom: Fix xscom error logging caused due to xscom OPAL call
xscom: Fix xscom error logging caused due to xscom OPAL call

Commit 80fd2e963bd4 ("xscom: Don't log xscom errors caused by OPAL
calls") ensured that xscom errors caused due to XSCOM read/write OPAL
calls aren't logged in the error-log since the caller of the OPAL call
is expected to handle it.

However we are continuing to print the prerror() in the OPAL log
regarding the same. This patch reduces the severity of the log from
PR_ERROR to PR_INFO for the xscom read and write made via OPAL calls.

Tested-by: Pavaman Subramaniyam <pavsubra@in.ibm.com>
Signed-off-by: Gautham R. Shenoy <c13571dbffa0eb89c7f8eebdce482897b0f5a685@linux.vnet.ibm.com>

Print info only for xscom read/writes made via opal calls

Signed-off-by: Gautham R. Shenoy <c13571dbffa0eb89c7f8eebdce482897b0f5a685@linux.vnet.ibm.com>
Signed-off-by: Vasant Hegde <a6d753843573f7bfed5075c1e875b0be8007a0ab@linux.vnet.ibm.com>

shenki/skiboot,shenki/skiboot,legoater/skiboot,open-power/skiboot,legoater/skiboot,open-power/skiboot,open-power/skiboot,shenki/skiboot,legoater/skiboot,qemu/skiboot,qemu/skiboot,qemu/skiboot,shenki/skiboot,open-power/skiboot,qemu/skiboot,legoater/skiboot,open-power/skiboot,shenki/skiboot,qemu/skiboot,legoater/skiboot