Force reconfig loop when clock deconfig is requested
Force reconfig loop when clock deconfig is requested

In general any deconfiguration during the IPL will end the istep
and trigger a reconfig loop (reboot).  However, this only works
if there is an actual target to deconfigure.  In the case of
clocks there is not a target.  Therefore if we detect a request
to deconfigure a clock we will artificially set the flag to force
a reconfig loop.

Special note - There is a possibility of an infinite loop with
this change because nothing will actually be deconfigured.  We
are going to live with this scenario because any real clock
error should be rediscovered when clock_test runs on the reboot.
At that point the appropriate deconfigs/guards/failovers/etc
will take place.

Change-Id: I7d5bc51fa75d156823a89eb22309533e2feb9cc6
CQ: SW544727
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/128075
Reviewed-by: Deborah L McLemore <1938e6bc52a6fb400ff401d42bc5360c2c7aaa30@us.ibm.com>
Tested-by: Jenkins OP Build CI <e610bd72261d3c0a48f1e8ae36832ab00774d426@us.ibm.com>
Reviewed-by: Isaac Salem <c69ff4695291efa8bfa4efde6e5e177cdf719186@ibm.com>
Tested-by: Jenkins Server <8e3f934e4c44875bc48d33da3ea13d93ba9a233f@us.ibm.com>
Tested-by: Jenkins Combined Simics CI <8312af3886dfc9bb930f549023677220805b137e@us.ibm.com>
Tested-by: FSP CI Jenkins <aa9e4d9ac7cd25905e9c0dd36d4150516e73dd86@us.ibm.com>
Reviewed-by: Daniel M Crowell <912029ca9254ac7b5854e56910561d682e1fa2d0@us.ibm.com>
Reviewed-by: Nick Bofferding <fb8db48116bc8a69e29dd8cdb037246f232f4af5@us.ibm.com>
Tested-by: Jenkins OP HW <0eb0fff262f74a65a832afbcc7b153e391c9a3fd@us.ibm.com>
Tested-by: Hostboot CI <52521565bd8ea18a2b112942dce4f4220a97c2c8@us.ibm.com>

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