PM: refine enablement attributes for advanced functions (VDM,RESCLK,WOF,IVRM)

- Move to a "disable feature" attribute paradigm for SYSTEM control
- Add consistent system enablement (eg Cronus, MRW) control attributes
- Added HWP attributes to allow p9_pstate_parameter_block to indicate
  validation status to p9_hcode_image_build for Hcode header updates
- Mark attributes as deprecated for future removal
- Added HB system defaults to auto enable RESCLK, VDM and WOF.  IVRM is
  disabled.
    - RESCLK only has override attributes so will enable function once code
      that looks the attributes is in a driver
    - VDM enablement forces the need for #W to be there and valid.  Valid will
      be if #W is all zero, disable VDMs;  if any of #W is non-zerom, failing
      validity checks (non-decreasing VID Compares) will fail the IPL.
    - WOF enablement needs IQ to fill out the OCC parameter block.  If
      not present, WOF is disabled.  Longer term (future commit), RESCLKs and
      VDMs will also gate WOF but not for early development and testing.
- Add a Chip EC attribute to discern the DD levels that WOF is supported
- Move to IVRM vs IVRMS
- Made all *ENABLED HWP attributes PROC_CHIP in scope to avoid collisions from
  multiple chip targets
- Made all HWP attributes writeable
- Deprecate (preped rename) an HWP attribute
- Added throttle control attributes

Change-Id: I5e56a36a9e2a4b3e6964ed66ff5c1013be26ed33
RTC: 173673
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/40063
Dev-Ready: Gregory S. Still <stillgs@us.ibm.com>
Tested-by: PPE CI <ppe-ci+hostboot@us.ibm.com>
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Reviewed-by: Michael S. Floyd <mfloyd@us.ibm.com>
Tested-by: Hostboot CI <hostboot-ci+hostboot@us.ibm.com>
Reviewed-by: CHRISTOPHER M. RIEDL <cmriedl@us.ibm.com>
Reviewed-by: Matt K. Light <mklight@us.ibm.com>
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>
Reviewed-by: Jennifer A. Stofer <stofer@us.ibm.com>
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/40089
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>

1 files changed, 56 insertions, 0 deletions

diff --git a/src/import/hwpf/fapi2/xml/attribute_info/hb_temp_defaults.xml b/src/import/hwpf/fapi2/xml/attribute_info/hb_temp_defaults.xml
index 9c943a7df..b03bfc288 100644
--- a/src/import/hwpf/fapi2/xml/attribute_info/hb_temp_defaults.xml
+++ b/src/import/hwpf/fapi2/xml/attribute_info/hb_temp_defaults.xml
@@ -202,15 +202,71 @@
         <default>0x00</default>
     </attribute>
 
+    <!--  set to 0 to allow automatic enablement when underlying support is available
+          VDM will simply not be enabled if any of the validation fails
+          eg ATTR_VDM_ENABLED will not be set by the HWP -->
+    <attribute>
+        <id>ATTR_SYSTEM_VDM_DISABLE</id>
+        <default>0x00</default>
+    </attribute>
+
+    <!-- Deprecated in deference to ATTR_VDM_ENABLED.  Will be deleted in the future -->
     <attribute>
         <id>ATTR_VDM_ENABLE</id>
         <default>0x00</default>
     </attribute>
+    <!-- End Deprecated -->
+
+    <!-- HWP attribute -->
+    <attribute>
+        <id>ATTR_VDM_ENABLED</id>
+    </attribute>
+
+    <!--  set to 0 to allow automatic enablement when underlying support is available -->
+    <attribute>
+        <id>ATTR_SYSTEM_RESCLK_DISABLE</id>
+        <default>0x00</default>
+    </attribute>
+
+    <!-- HWP attribute -->
+    <attribute>
+        <id>ATTR_RESCLK_ENABLED</id>
+    </attribute>
+
+    <!--  set to 0 to allow automatic enablement when underlying support is available -->
+    <attribute>
+        <id>ATTR_SYSTEM_IVRM_DISABLE</id>
+        <default>0x00</default>
+    </attribute>
+    <attribute>
+        <id>ATTR_IVRM_ENABLED</id>
+    </attribute>
 
+    <!-- Deprecated in deference to ATTR_SYSTEM_WOF_ENABLE.  Will be deleted in the future -->
     <attribute>
         <id>ATTR_SYSTEM_WOF_ENABLED</id>
         <default>0x00</default>
     </attribute>
+    <!-- End Deprecated -->
+
+    <!--  set to 0 to allow automatic enablement when underlying support is available
+          WOF will simply not be enabled if any of the validation fails
+          eg ATTR_WOF_ENABLED will not be set by the pstate_parameter_block HWP -->
+    <attribute>
+        <id>ATTR_SYSTEM_WOF_DISABLE</id>
+        <default>0x00</default>
+    </attribute>
+
+    <!-- HWP attribute -->
+    <attribute>
+        <id>ATTR_WOF_ENABLED</id>
+        <default>0x00</default>
+    </attribute>
+
+    <attribute>
+        <id>ATTR_SYSTEM_PSTATES_MODE</id>
+        <default>0x00</default>
+    </attribute>
 
     <attribute>
         <id>ATTR_MSS_PHY_SEQ_REFRESH</id>