summaryrefslogtreecommitdiff
path: root/meta-ibm/meta-witherspoon/recipes-phosphor/configuration
AgeCommit message (Collapse)AuthorFilesLines
2020-02-06Value setting for IPMI clear security keysJayashankar Padath1-0/+12
Support to set the value for ClearSecurityKeys property which can be used to indicate when certain security keys need to be cleared or reset those values back to its default state from the system by the host. This property is mapped to an IPMI sensor and default value will be zero. Setting this property does not gurantee a successful operation as additional conditions like the physical presence pin or jumper settings will be checked by the host to clear/reset the sensitive data. Tested: Verified that the property is getting created with the expected default value as zero and can be updated to different values using ipmitool or busctl command. 1. Default value output: busctl get-property xyz.openbmc_project.Settings /org/open_power/control/host0/ClearHostSecurityKeys org.open_power.Control.TPM.SecurityKeys ClearHostSecurityKeys y 0 ipmitool -I lanplus -H 9.3.185.33 -U root -P 0penBmc raw 0x04 0x2D 0xE8 00 40 00 00 2. Set to a new value as 5 using busctl command: busctl set-property xyz.openbmc_project.Settings /org/open_power/control/host0/ClearHostSecurityKeys org.open_power.Control.TPM.SecurityKeys ClearHostSecurityKeys y 5 3. After setting to a new value as 5: ipmitool -I lanplus -H 9.3.185.33 -U root -P 0penBmc raw 0x04 0x2D 0xE8 05 40 00 00 4. ipmitool command to set the value as 4 ipmitool -I lanplus -H 9.3.185.33 -U root -P 0penBmc raw 0x04 0x30 0xE8 0x00 0x04 0x00 0x00 0x00 0x00 0x00 0x00 0x00 ipmitool -I lanplus -H 9.3.185.33 -U root -P 0penBmc raw 0x04 0x2D 0xE8 09 40 00 00 5. Invalid value test o/p: ipmitool -I lanplus -H 9.3.185.33 -U root -P 0penBmc raw 0x04 0x30 0xE8 0x00 0x12C 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Given data "0x12C" is invalid. (From meta-ibm rev: 81a9143100d5d4a7d97350afa1794be694d45590) Signed-off-by: Jayashankar Padath <jayashankar.padath@in.ibm.com> Change-Id: I9e12b6e5abb3a9b198921847605a74b771fd9945 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-11-20meta-ibm: Modify ipmi configBen_Pai1-56/+56
We think fan is a necessary sensor in ipmi sensor list. Tested: Use ipmitool sdr to check it. (From meta-ibm rev: 5bdc8591ac5e6ce708fdc0788806cb89452c3b14) Change-Id: I87acef1dcfe11bc532eac5412375133b56f40320 Signed-off-by: Ben Pai <Ben_Pai@wistron.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-10-17Extra argument to IPMI parsersSantosh Puranik1-4/+5
This commit adds an option to the invocation of IPMI MRW parsers within the IBM layer to allow them to parse an incomplete MRW. The extra option is only enabled for the Rainier machine. Tested: I updated rainier.conf to point to the in progress Rainier MRW and made sure that with the new option in the recipe, the IPMI parsers no longer complained about a broken MRW. (From meta-ibm rev: 7c056f4b459fa67dc911b40e14055b86dbf1ef46) Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com> Change-Id: I4482a09c93ab727b7330946f61e52a8ec92753fc Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-19meta-ibm: Add mihawk total power sensorBen_Pai1-2/+23
Get total power from occ. (From meta-ibm rev: 5f74841d980f274383dd0bf1c16b1c3df18142e2) Signed-off-by: Ben Pai <Ben_Pai@wistron.com> Change-Id: I97bf6b2229890dca1a0bda421b85b10392c2a814 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-18meta-ibm: Remove references to IBMBASEBrad Bishop1-1/+1
IBMBASE is only used for pointing at licenses...point at the licenses in oe-core in meta/files/common-licenses instead. to match the defacto convention used in other oe layers like meta-openembedded. (From meta-ibm rev: cbbb0e5b4e44d831fce5daafd13272d401440f40) Change-Id: Ib214f92b2c384e3eb2a1f53ecf4b21034438d001 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-09-12meta-ibm: Add mihawk ipmi yaml.Ben_Pai3-3/+597
Add mihawk's ipmi sensor and fru yaml. Tested: Use ipmi command to get the sensor list and fru data. (From meta-ibm rev: 05c9a2734de75271837313f0e1794c58df50e990) Signed-off-by: Ben Pai <Ben_Pai@wistron.com> Change-Id: Ic85af9b0cc1b44a3377fa919e63ab04dbff7a31c Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-26swift-ipmi: Hard coded sensor supportAndrew Geissler4-117/+591
The Swift MRW has been updated and this commit utilizes some unused sensors for Swift starting at 0xFE and counting backwards (From meta-ibm rev: df212c93689bd73f0e760ed3cfffada6fa6b9ffa) Change-Id: Ica981d322f51fec94c0db94884938a60b637eb73 Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-23Add Accelerator Interface to GPU SensorsSantosh Puranik1-0/+1
This commit adds the xyz.openbmc_project.Inventory.Item.Accelerator interface to IPMI GPU functional sensors. This was something done earlier by commit f510f7b6b708b22db1f08faf369994f01edd0ddc. The same is being ported now to the new sensor config YAML. Tested: Loaded this change up on a witherspoon. Verified that the inventory objects created by host-ipmid now implement the xyz.openbmc_project.Inventory.Item.Accelerator interface. busctl call xyz.openbmc_project.ObjectMapper /xyz/openbmc_project/object_mapper xyz.openbmc_project.ObjectMapper GetSubTree sias "/xyz/openbmc_project/inventory" 0 1 "xyz.openbmc_project.Inventory.Item.Accelerator" a{sa{sas}} 6 "/xyz/openbmc_project/inventory/system/chassis/motherboard/gv100card0" .... .... (From meta-ibm rev: 2b99559bff775f719fb79a5a770b5267bbbd6dcc) Signed-off-by: Santosh Puranik <santosh.puranik@in.ibm.com> Change-Id: Ic132c417aca171e23f5d72705461fe3378e194b0 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-10swift-ipmi: Add in bmc fru configAndrew Geissler2-0/+120
Refactor the config yaml to be machine specific The only rule is the values in this file not conflict with the FRU_ID fields in the Swift MRW. Swift MRU has FRU_ID values that go into the 50s so just add 10 to all values in this file. (From meta-ibm rev: 89af26a2ca92f79493a652ae279a6c48a67d1f7f) Change-Id: I4a2e3ca95791d0ec2201b027894833a7ef7b4cfb Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-07-10swift-ipmi: Add support for non-host based configAndrew Geissler2-0/+21
The Swift MRW does a few things different here: - Renames these from gv100 to ga100 - Starts their FRU_ID at 15 - Only has 4 vs. 6 of them (From meta-ibm rev: 91a87c8b0288f235452b3073e24a5519020553e8) Change-Id: I0af55e2d0bf5e317dfae45b4e53810d3b6d8897c Signed-off-by: Andrew Geissler <geissonator@yahoo.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2019-06-19meta-ibm: acx22: new YAML config recipeBrad Bishop8-0/+1212
YAML configuration files exist scattered throughout the OpenBMC tree and how they are used is controlled with layers dependencies of virtuals and preferred providers. Most of the time the above scheme is very difficult to comprehend. This patch continues a re-thinking of that approach towards a more centralized scheme. Specifically this patch implements a single YAML config recipe for the ACx22 systems. The logic contained in the recipe was pulled from all over the OpenBMC tree - the ability to comprehend how the different YAML files are generated and consumed should be greatly eased. A couple notable details: - Specialized tasks for doing deep YAML dictionary merges existed in the upstream recipes (-hardcoded.yaml, -config.yaml), but it was observed that simply concatenating the YAML files produced the same results, so the specialized deep merge logic was not copied here and can be deprecated upstream. - Unlike the upstream recipes, acx22-yaml-config is a target recipe and as such enables MACHINE based overrides. YAML files were copied from different locations in the tree, and run through a styling application (pyyaml dump(load(yaml))): phosphor-ipmi-fru-read-bmc-inventory-native:bmc-fru-config.yaml -> acx22-yaml-config:acx22-ipmi-fru-bmc.yaml phosphor-ipmi-fru-read-not-sent-by-host-inventory-native:fru-config-not-sent-by-host.yaml -> acx22-yaml-config:acx22-ipmi-fru-not-sent-by-host.yaml phosphor-ipmi-host:occ_sensors.hardcoded.yaml -> acx22-yaml-config:acx22-ipmi-occ-sensors.yaml phosphor-ipmi-host:hwmon_sensors.hardcoded.yaml -> acx22-yaml-config:acx22-ipmi-hwmon-sensors.yaml phosphor-ipmi-host:witherspoon_hwmon_sensors.hardcoded.yaml -> acx22-yaml-config:ac922-ipmi-extra-hwmon-sensors.yaml phosphor-ipmi-sensor-inventory-mrw-config-native:config.yaml -> acx22-yaml-config:acx22-ipmi-sensors-mrw.yaml (From meta-ibm rev: 3cb4a62140dca941e801026f447f13374cf68968) Change-Id: Id0584812bbf40c0118c8c4383d9dd67c38a45dec Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
generated by cgit v1.2.3 (git 2.39.0) at 2024-09-03 17:00:26 +0300