bmcweb: Add Warthog OEM Support

Expose all Warthog GPIO values as Warthog OEM for easiler acces ad part
of the work to deprecate old method of log entries.

Tested:
```
{
 "@odata.id": "/redfish/v1/Systems/system/Storage/warthog_storage_1#/StorageControllers/1",
 "@odata.type": "#Storage.v1_9_1.StorageController",
 "Links": {
   "Google": {
     "Warthog": {
       "@odata.type": "#GoogleWarthog.v1_0_0.GoogleWarthog",
       "BootFailureCount": 0,
       "DebugMode": false,
       "DisableWatchdog": false,
       "FruEepromWriteProtect": true,
       "ManufacturingMode": false,
       "MorristownOtpWriteEnable": false,
       "MorristownOtpWriteProtect": false,
       "Name": "Warthog GPIO Action Info",
       "PwrseqPgood": true,
       "PwrseqState": "PgoodPlpOk",
       "SpiImgSelect": 0,
       "TriggerPowerCycle": false,
       "WatchdogTriggered": false
     }
   }
 },
 ...
}
```

Google-Bug-Id: 270449147
Google-Bug-Id: 245814416
Google-Bug-Id: 239578152
Change-Id: I2724e86bc3178f7d81980a8cfb2b8e9e41516242
2 files changed
tree: b018b98d8498abf5854385535157bf269697c142
  1. conf/
  2. dynamic-layers/
  3. meta-nuvoton-npcm8xx/
  4. recipes-connectivity/
  5. recipes-core/
  6. recipes-google/
  7. recipes-kernel/
  8. recipes-phosphor/
  9. LICENSE
  10. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.