/openbmc/phosphor-power/phosphor-regulators/src/ |
H A D | vpd.hpp | 37 class VPD class 41 VPD() = default; 42 VPD(const VPD&) = delete; 43 VPD(VPD&&) = delete; 44 VPD& operator=(const VPD&) = delete; 45 VPD& operator=(VPD&&) = delete; 46 virtual ~VPD() = default; 75 class DBusVPD : public VPD
|
H A D | services.hpp | 90 virtual VPD& getVPD() = 0; 150 virtual VPD& getVPD() override in getVPD()
|
/openbmc/openbmc-test-automation/openpower/vpd/ |
H A D | test_vpd_tool.robot | 2 Documentation This suite tests System Vital Product Data (VPD) using vpdtool. 23 Verify System VPD Data Via Vpdtool 24 [Documentation] Verify the system VPD details via vpdtool output. 26 [Template] Verify VPD Data Via Vpdtool 34 Verify VPD Component Read 35 [Documentation] Verify details of all VPD component via vpdtool. 41 Verify VPD Component Read Operation ${component} 45 Verify VPD Field Read 46 [Documentation] Verify reading VPD field value via vpdtool. 57 Verify VPD Field Read Operation ${component} [all …]
|
/openbmc/docs/designs/ |
H A D | vpd-collection.md | 1 # VPD collection app on OpenBMC 9 On OpenBMC, Vital Product Data (VPD) collection is limited to only one or two 11 systems, the BMC also supports just one VPD format, the [OpenPower VPD] [1] 13 VPD, which the BMC currently does not support. Certain FRUs also have keyword 14 format VPD. 16 The BMC requires to read VPD for all FRUs for several reasons: 18 - Some of the VPD information such as FRU part number, serial number need to be 26 - There are use cases for the BMC to send VPD data to the host 28 get VPD that is not directly accessible to it. 30 The VPD data itself may reside on an EEPROM (typical) or may be synthesized out [all …]
|
H A D | entity-manager-hw-id-vpd-discover-via-device-tree.md | 1 # Entity-Manager HW ID: VPD Discovery via Device-Tree Properties 21 (VPD) - for the baseboard as a FRU storage blob held in a physical EEPROM. 29 Additionally, a separate daemon for handling OpenPower format VPD is hosted in 37 Once VPD is made available on D-Bus, it can be referenced by the Entity-Manager 41 HPE platforms provide the following properties for baseboard VPD: 52 HPE platforms in Gen 10 and earlier provided VPD through a standard 57 firmware communicates with a secure element to provide necessary VPD. This 61 providing VPD from the secure element. 64 HPE-specific bootloader in the block fetches the VPD blob from the secure 118 may be populated using retrieved VPD values as appropriate to offer a D-Bus [all …]
|
H A D | psu-monitoring.md | 17 various faults, and report vital product data (VPD). Some of the function will 52 6. The power supply application must collect and report power supply VPD (unless 53 that VPD is collected and reported via another application reading an EEPROM 94 on, which supplies are present, if the power supply is ready for reading VPD 140 - Power supply VPD data reported for present power supplies.
|
/openbmc/openpower-vpd-parser/ |
H A D | README.md | 3 This repository hosts code for OpenPower and IBM IPZ format VPD parsers. Both 4 OpenPower VPD and IPZ VPD formats are structured binaries that consist of 11 ## OpenPower VPD Parser 13 This is a build-time YAML driven application that parses the OpenPower VPD 18 - How VPD data is translated into D-Bus interfaces and properties. 20 The application instance must be passed in the file path to the VPD (this can, 24 ## IBM VPD Parser 27 option. This parser differs from the OpenPower VPD parser in the following ways: 29 - It parses all the records and keywords from the VPD, including large keywords 33 representing the VPD for a given VPD file path. [all …]
|
H A D | meson_options.txt | 1 option('BUSNAME', type : 'string', value : 'com.ibm.VPD.Manager',description : 'BUS NAME FOR THE SE… 2 option('OBJPATH', type : 'string', value : '/com/ibm/VPD/Manager', description : 'OBJECT PATH FOR T… 3 option('IFACE', type : 'string', value : 'com.ibm.VPD.Manager', description : 'INTERFACE NAME') 7 …JSON file that defines inventory blueprint. The default path before system VPD service sets up the… 10 …ing', value: '/sys/bus/i2c/drivers/at24/8-0050/eeprom', description: 'EEPROM path of system VPD.') 11 …TH', type: 'string', value: '/var/lib/vpd', description: 'Symlink folder for VPD invnetory JSONs')
|
/openbmc/phosphor-dbus-interfaces/gen/com/ibm/VPD/ |
H A D | meson.build | 5 sdbusplus_current_path = 'com/ibm/VPD' 9 input: ['../../../../yaml/com/ibm/VPD.errors.yaml'], 22 'com/ibm/VPD', 30 'com/ibm/VPD/Collection__markdown'.underscorify(), 31 input: ['../../../../yaml/com/ibm/VPD/Collection.interface.yaml'], 44 'com/ibm/VPD/Collection', 52 'com/ibm/VPD/Manager__markdown'.underscorify(), 53 input: ['../../../../yaml/com/ibm/VPD/Manager.interface.yaml'], 66 'com/ibm/VPD/Manager',
|
/openbmc/phosphor-dbus-interfaces/yaml/com/ibm/ipzvpd/ |
H A D | README.md | 1 # IPZ VPD D-Bus Interfaces 3 IPZ is a VPD (Vital Product Data) format used in IBM Power systems. The format 8 The [OpenPower VPD][1] format is quite similar to the IPZ format and describes 11 Also refer to the [VPD Collection design document][2] that describes how the VPD 12 collection application on the BMC will parse and publish the VPD data for IBM 15 The D-Bus interfaces defined here describe how IPZ VPD will be made available on 16 D-Bus. Each YAML here represents a record in the IPZ VPD and keywords that
|
/openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
H A D | compare_vpd.md | 5 Compares a VPD (Vital Product Data) keyword value to an expected value. 7 VPD is information that describes a hardware component. VPD is typically read 8 from an EEPROM on a Field-Replaceable Unit (FRU). For this reason, VPD is also 11 The phosphor-regulators application obtains VPD keyword values from D-Bus. Other 12 BMC applications and drivers are responsible for reading VPD from hardware 15 The following VPD keywords are currently supported: 24 a VPD keyword value. For example, you could set the output voltage only for 32 - An error occurred while attempting to read VPD from the hardware component. 33 - The BMC cannot access the VPD due to the system hardware design, such as not 49 … | string | Field-Replaceable Unit (FRU) that contains the VPD. Specify the relati… [all …]
|
/openbmc/openpower-vpd-parser/vpd-tool/ |
H A D | README.md | 1 # VPD Tool Overview 3 VPD Tool is designed for managing BMC system FRU's Vital Product Data(VPD). It 4 provides command line interface to read and write FRU's VPD. More information 6 [here](https://github.ibm.com/openbmc/openbmc/wiki/VPD-TOOL-HELPER).
|
/openbmc/u-boot/board/ge/common/ |
H A D | Kconfig | 2 hex "I2C address of the EEPROM device used for VPD" 4 VPD = Vital Product Data 7 int "I2C bus of the EEPROM device used for VPD." 10 int "Size in bytes of the EEPROM device used for VPD" 13 int "Number of bytes to use for VPD EEPROM address"
|
/openbmc/phosphor-dbus-interfaces/gen/com/ibm/ |
H A D | meson.build | 5 subdir('VPD') subdir 12 input: ['../../../yaml/com/ibm/VPD.errors.yaml'], 13 output: ['VPD.md'], 25 'com/ibm/VPD',
|
/openbmc/phosphor-dbus-interfaces/gen/com/ibm/VPD/Manager/ |
H A D | meson.build | 3 sdbusplus_current_path = 'com/ibm/VPD/Manager' 6 'com/ibm/VPD/Manager__cpp'.underscorify(), 7 input: ['../../../../../yaml/com/ibm/VPD/Manager.interface.yaml'], 26 'com/ibm/VPD/Manager',
|
/openbmc/phosphor-dbus-interfaces/gen/com/ibm/VPD/Collection/ |
H A D | meson.build | 3 sdbusplus_current_path = 'com/ibm/VPD/Collection' 6 'com/ibm/VPD/Collection__cpp'.underscorify(), 7 input: ['../../../../../yaml/com/ibm/VPD/Collection.interface.yaml'], 26 'com/ibm/VPD/Collection',
|
/openbmc/openpower-vpd-parser/scripts/ |
H A D | wait-vpd-status.sh | 7 …output=$(busctl get-property com.ibm.VPD.Manager /com/ibm/VPD/Manager com.ibm.VPD.Manager Collecti…
|
/openbmc/openbmc-test-automation/systest/collection/ |
H A D | bmc_collect_vpd_and_hw_status.robot | 2 Documentation BMC server health, collect VPD and hardware status. 21 Rest Collect VPD And Hardware Status 22 [Documentation] Collect VPD and hardware status using the OpenBMC Rest API. 39 Redfish Collect VPD And Hardware Status 40 [Documentation] Collect VPD and hardware status using Redfish.
|
/openbmc/openbmc-test-automation/openpower/ |
H A D | check_vpd_and_hw_status.robot | 2 Documentation BMC collect VPD and hardware status. 18 Collect VPD And Hardware Status 19 [Documentation] Collect VPD and hardware status using Redfish. 36 Run VPD Tool
|
/openbmc/openbmc-test-automation/extended/code_update/ |
H A D | host_code_update.robot | 76 Test Boot With No VPD Cache 79 ... VPD files and verify that the OS can still boot. 86 ... ls ${cache_files_dir_path} | grep VPD -c 89 ... msg=Missing VPD files at ${cache_files_dir_path}. 91 # Delete the *VPD* files. 92 BMC Execute Command rm -f ${xxx_dir_path}*VPD* 96 # After powering-on the system, the VPD files should be present. 98 ... ls ${cache_files_dir_path} | grep VPD -c 100 ... msg=Three VPD files expected at ${cache_files_dir_path}. 102 # Power off. The next test case will boot the OS with the new VPD files.
|
/openbmc/linux/drivers/nvmem/layouts/ |
H A D | Kconfig | 6 tristate "Kontron sl28 VPD layout support" 9 Say Y here if you want to support the VPD layout of the Kontron
|
/openbmc/openpower-vpd-parser/service_files/ |
H A D | vpd-manager.service | 2 Description=VPD Manager 14 BusName=com.ibm.VPD.Manager
|
/openbmc/entity-manager/ |
H A D | meson.options | 5 description: 'Build fru-device VPD parser.', 23 description: 'Build device-tree VPD parser',
|
/openbmc/openbmc/meta-openpower/recipes-phosphor/vpd/ |
H A D | openpower-fru-vpd_git.bb | 1 SUMMARY = "Parser for OpenPOWER-format FRU VPD" 2 DESCRIPTION = "Parse OpenPOWER-format FRU VPD and update inventory"
|
/openbmc/openbmc-test-automation/docs/ |
H A D | openbmc_test_tools.md | 234 ## VPD tool: 236 VPD tool is designed for managing BMC system FRU's Vital Product Data(VPD). It 237 provides command line interface to read and write FRU's VPD. Refer 238 [VPD TOOL README](https://github.com/openbmc/openpower-vpd-parser/blob/master/vpd-tool/README.md)
|