Clean up FAR3BQ workaround so that fails will be committed properly
Clean up FAR3BQ workaround so that fails will be committed properly

Before we were using the FAPI infrastructure to scom the register
but we need to use the native scom to handle errors correctly

Change-Id: I39b244497265f61efaeba8685d4a39fb41cf8646
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/34938
Tested-by: Jenkins Server <8e3f934e4c44875bc48d33da3ea13d93ba9a233f@us.ibm.com>
Tested-by: Jenkins OP Build CI <e610bd72261d3c0a48f1e8ae36832ab00774d426@us.ibm.com>
Tested-by: FSP CI Jenkins <aa9e4d9ac7cd25905e9c0dd36d4150516e73dd86@us.ibm.com>
Reviewed-by: Martin Gloff <df0a4963746ae04ab678d064fccc7ee68adfd751@us.ibm.com>
Reviewed-by: Corey V. Swenson <6b585c7446d4a0351ef146912eaabcae3d9a2e28@us.ibm.com>
Reviewed-by: Daniel M. Crowell <912029ca9254ac7b5854e56910561d682e1fa2d0@us.ibm.com>

open-power/hostboot,open-power/hostboot,open-power/hostboot,open-power/hostboot,open-power/hostboot