Force Update of Minimum Secure Version to 2 for Early Ship Customers
Force Update of Minimum Secure Version to 2 for Early Ship Customers

This commit looks for and handles a special case in regards to
the system's Minimum Secure Version (MSV):
- If the MSV lockin policy is false --AND--
- The current Minimum Secure Version is < 2 -- AND --
- Secureboot is enabled...
Then set the minimum secure version to 2.

This is considered a special case because the MSV lockin policy is
being overruled and the value of 2 is not necessarily the exact
incoming MSV value.

This change is necessary for early ship customers who might get a
driver with SV==0, possibly loaded the initial GA driver of SV==1,
but we want to automatically update them to at least 2 once they get
an official production build with necessary security changes without
making them use the ASMI "Lockin Policy" option.

Change-Id: I8c83ddb59b74c64ff0ea6484162f33347294674b
CQ:SW535469
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/123038
Tested-by: Jenkins Server <8e3f934e4c44875bc48d33da3ea13d93ba9a233f@us.ibm.com>
Tested-by: Jenkins OP Build CI <e610bd72261d3c0a48f1e8ae36832ab00774d426@us.ibm.com>
Reviewed-by: Christopher J Engel <806c4899b4b629cf3b8af1d2b7c931cc9efb35b5@us.ibm.com>
Tested-by: Jenkins OP HW <0eb0fff262f74a65a832afbcc7b153e391c9a3fd@us.ibm.com>
Tested-by: FSP CI Jenkins <aa9e4d9ac7cd25905e9c0dd36d4150516e73dd86@us.ibm.com>
Tested-by: Jenkins Combined Simics CI <8312af3886dfc9bb930f549023677220805b137e@us.ibm.com>
Tested-by: Hostboot CI <52521565bd8ea18a2b112942dce4f4220a97c2c8@us.ibm.com>
Reviewed-by: Nicholas E Bofferding <fb8db48116bc8a69e29dd8cdb037246f232f4af5@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