summaryrefslogtreecommitdiffstats
path: root/meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/recipes-phosphor/ipmi
Commit message (Collapse)AuthorAgeFilesLines
* [Subtree] Bring openbmc machines to top levelDave Cobbley2018-08-2314-982/+0
| | | | | | | | | The new subtree model brings the subtrees up from the openbmc-machines layer. Change-Id: I58a03ae1be374bc79ae1438e65e888375d12d0c0 Signed-off-by: Dave Cobbley <david.j.cobbley@linux.intel.com> Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
* Add witherspoon specific channel.yamlNagaraju Goruganti2018-06-042-0/+9
| | | | | | | | | | channel.yaml keeps the info about number of available Ethernet channels on the given machine. Resolves openbmc/openbmc#3191 Change-Id: I904e02a96bb6f295c6456b8a8ba26e756c218df0 Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
* wspoon: Remove GPU power sensorsMatt Spinler2018-05-221-131/+0
| | | | | | | | | | | | | | | | | | | The power values being displayed were basically instantaneous readings as measured by the APSS monitor device, and as such could show a lot of peaks and valleys that would be undesirable to surface. In the future they may get added back in with some averaging done. In the meantime, the user can use the nvidia-smi command line tool on the host to get the proper power values. Tested: No GPU power sensors in D-Bus. Resolves openbmc/openbmc#3183 Change-Id: Ie2d92560867f29dbf852c53c55b8d371f5fef06f Signed-off-by: Matt Spinler <spinler@us.ibm.com>
* wspoon: Rename GPU power sensors in IPMI YAMLMatt Spinler2018-05-221-6/+6
| | | | | | | | | The GPU power hwmon sensors recently changed names to match the GPU temperature sensor naming conventions. Update this YAML to reflect that. Change-Id: I5100ee514bed3ec7901deddcfd3bd9d619d8cd51 Signed-off-by: Matt Spinler <spinler@us.ibm.com>
* witherspoon: Add support for GPU FRUSNagaraju Goruganti2018-05-102-0/+30
| | | | | | | | | | | -commit #f24faab provides basic infra for FRUs which are accessible through host but host is not sending the details for those FRUs. -GPU FRUs are of type mentioned at commit #f24faab.This commit hardcodes the WITHERSPOON GPU FRU info into YAML. Change-Id: I783bf77d8e95abf687d2605e2c97a5bb10504c70 Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
* phosphor-ipmi-host: Move configuration to phosphor-ipmi-configAndrew Jeffery2018-05-107-48/+103
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Witherspoon requires an dev_id.json file whose content is partially derived from data provided by the os-release package. os-release is updated for each commit, as some of its content (VERSION and VERSION_ID) can be derived from `git describe`. As dev_id.json was provided by the phosphor-ipmi-host package, every commit transitively triggered a rebuild of phosphor-ipmi-host in order to satisfy Witherspoon's requirements. Always rebuilding phosphor-ipmi-host is unhelpful for several reasons: * It needlessly reduces CI throughput, as it is likely the commits in question do not modify the phosphor-ipmi-host package. * GCC suffers from what appears to be an unfixable[1] bug[2] that causes phoshor-ipmi-host to consume large (>5GiB) amounts of RAM when compiling some (at least Witherspoon) sensor configurations. To avoid this, separate the configuration files out into virtual/phosphor-ipmi-config and phosphor-ipmi-config packages that phosphor-ipmi-host RDEPENDS on. Witherspoon provides an alternative implementation in witherspoon-ipmi-config to mangle dev_id.json to its particular requirements. A virtual is used rather than a simple bbappends for Witherspoon, as the bbappend approach breaks builds of machines other than Witherspoon if Witherspoon is built first: The Witherspoon-specific dev_id.json file is deployed in its mangled form into e.g. a Zaius image. Specifically, the following sequence will trigger the issue: $ TEMPLATECONF=.../witherspoon.conf . openbmc-env $ bitbake obmc-phosphor-image $ rm -rf conf $ TEMPLATECONF=.../zaius.conf . openbmc-env $ bitbake obmc-phosphor-image [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80290#c26 [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80290 Change-Id: Ib9629fc77b29e2deeab3f1c3a145d9e966c14ec4 Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
* Add cipher list json to the Witherspoon imageTom Joseph2018-04-242-0/+39
| | | | | | | | | | | | | | | | For IPMI v2.0/RMCP+ sessions, authentication, integrity and confidentiality algorithms are involved. The algorithms used in combination are called Cipher Suites. Each cipher suite has the id as the key and a collection of algorithms. Each algorithm has a number assigned in the IPMI specification. Cipher data information can be read by the Get Channel Cipher suites command, and the RMCP+ messaging Cipher Suite entries support and the RMCP+ messaging Cipher Suite Entries parameter of the Get LAN configuration parameters command. Change-Id: I3460046a0c72acd5cb2f9066f264142a2378120c Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
* openpower:added "mutability"Jayanth Othayoth2018-04-161-0/+2
| | | | | | | Added "mutability" flag to indicate if a sensor is READ/WRITE/RW. Change-Id: I3dcc27526adc2a5d6b1206e8beee66093220763a Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
* Generate IPMI Aux firmware revision from VERSION_ID fieldTom Joseph2018-03-261-0/+41
| | | | | | | | | | | | | | IPMI command get device id supports auxiliary firmware version field in the response. This field is 4 bytes and the first 2 bytes would contain the count from the version tag in BCD format, the next 2 bytes would represent the release version in BCD format. This change can support the VERSION_ID format of IBM enterprise build and a build from the master. Resolves openbmc/openbmc#2972 Change-Id: I4f4e23a3be687b814cef51b1b96c7b97778bcb16 Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
* Add power supply to BMC accessible FRUs to generate FRU mapNagaraju Goruganti2018-03-231-0/+50
| | | | | | | | | Adding power supply to BMC accessible FRUs. Partially Resolves openbmc/openbmc#2984 Change-Id: Ib4af12f281f433ecac727324ec75e95fd62b8714 Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
* Autogenerate output YAML for temperature sensors by parsing MRWMarri Devender Rao2018-03-231-1747/+10
| | | | | | | | | | | | | Added temperature sensors to input config YAML to auto generate output YAML entries by parsing the MRW Removed temperature sensors from the handcoded sensor YAML file Resolves openbmc/openbmc#2942 Resolves openbmc/openbmc#2982 Change-Id: I7ac43bdf51e37c78b66c57bbe0cba9cbef2c5e2e Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
* Add witherspoon hardware sensors for SDR mapping to DBus objectsMarri Devender Rao2018-03-012-0/+2442
| | | | | | | | | | | | | | The handcoded harware sensor yaml file is merged with the final sensor yaml file. phosphor-ipmi-sensor-inventory native recipe finds all the yaml files with extension ".hardcoded.yaml" and merges them to the final sensor yaml file Resolves openbmc/openbmc#2613 Change-Id: I3e25f1312a813fcba0070a3e778915f52edba7aa Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
* dcmi: add record id to Witherspoon sensors JSONDeepak Kodihalli2018-02-221-50/+50
| | | | | | | | Add SDR record id to Witherspoon sensors JSON. This will be consumed by the DCMI SDR Info command to provide record ids to a client. Change-Id: I032238871a000db40e771b1620723e70b92471bf Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
* dcmi: rename get temp readings jsonDeepak Kodihalli2018-02-162-1/+1
| | | | | | | | | Rename dcmi_temp_readings.json as dcmi_sensors.json. This will serve as the dcmi sensor config information to cater both the 'get temperature readings' and 'get sensor info' commands. Change-Id: Ia6f79330a4568be94555d8cb3f57eac23e486317 Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
* FRU: Add Entity ID in the host FRU inventory yamlRatan Gupta2018-02-141-40/+58
| | | | | | | | | | | | | | | This commit also adds the entityID and entityInstance property for BMC FRUS config yaml. These attributes are required to pass it through Get SDR command. Currently we support two types of record format through Get SDR 1) FULL Record. 2) FRU Record. Resolves openbmc/openbmc#2823 Change-Id: Ie7424fbc493dde5070a2c65c74ba83565154b9d4 Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
* sensor: Modify config for sensor to add additional fieldsTom Joseph2018-02-061-0/+6
| | | | | | | | | | Added entity ID, entity instance and sensor naming pattern to the generated sensor yaml. Resolves openbmc/openbmc#2612 Change-Id: Ie4dc9548833cb30126e873a7597b2be9b1ea7f79 Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
* DCMI: Get power reading - add witherspoon configMarri Devender Rao2018-02-012-0/+4
| | | | | | | | | The D-Bus object that captures the power reading varies from system to system, using JSON config file to specify the D-Bus object to read based on the sytem. Change-Id: I2bfac0826b051d243b4edba34cc0b0e09dc648cf Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
* dcmi : get temperature readings: witherspoon jsonDeepak Kodihalli2018-01-312-0/+59
| | | | | | | | This commit adds a json file that specifies instance numbers and d-bus paths to look-up for temperature readings. Change-Id: I501f75214042c5b1ad56e64d0893e142a90a2efc Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
* Add missing 'Offsets' key to the occ sensors yamlDeepak Kodihalli2018-01-181-0/+2
| | | | | | | | | The commit e245e4e932279a112325dae06d7c12cf9e8ed833 in phosphor-host-ipmid introduced a breaking change that requires sensor input yamls to have a key called 'Offsets'. Change-Id: I6be7c4cde2236752e0d7139f2b7cd2a26a1753d4 Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
* Get Device ID - JSON for WitherspoonDavid Cobbley2018-01-052-1/+5
| | | | | | | | | This is a reference for how to use get device ID with the witherspoon platform. All other platforms that need get device ID should add dev_id.json in their own machine specific bbappend files. Change-Id: I0348748bfb9442d2de43b661cc291663f279efcb Signed-off-by: David Cobbley <david.j.cobbley@linux.intel.com>
* Add BMC accessible FRUs to generate FRU mapMarri Devender Rao2017-08-302-0/+53
| | | | | | | | | | At present MRW does not have FRU ID's for BMC accessible FRUs, so supporting by hand coding the config details. Resolves openbmc/openbmc#1931 Change-Id: Ia33aa56378fe0e31df722b9134c041e66a5133d5 Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
* Merge hardcoded sensor yamls with generated sensor.yamlDhruvaraj Subhashchandran2017-08-082-0/+36
| | | | | | | | This change will enable adding sensors which is not part of the MRW to the MRW bases systems. Change-Id: I0d7d2ff94a668ae77bb8c906e85ef6280dc49830 Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
* ipmi: Remove virtual/phosphor-ipmi-fru-configBrad Bishop2017-02-021-14/+0
| | | | | | | | | | | | | | | | | Replace this virtual with two others: -virtual/phosphor-ipmi-fru-hostfw-config -virtual/phosphor-ipmi-fru-inventory. Update ipmi-fru-parser machine recipes to provide virtual/phosphor-ipmi-fru-inventory rather than virtual/phosphor-ipmi-fru-config. Remove machine recipes on machines that use MRW since a single MRW recipe provides for any MRW using system automatically. Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com? Change-Id: Ia0d94b938eb2c7bfadd5a018ae5ea136f14dd874
* Phosphor IPMI FRU config stubs for most systemsBrad Bishop2017-01-251-0/+14
Add native recipe stubs that (will) provide the the IPMI -> DBus inventory mapping for the Phosphor IPMI FRU provider. Change-Id: I21e76bc23ef1638ddcc318a179808521dea7f205 Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
OpenPOWER on IntegriCloud