Name Date Size #Lines LOC

..18-Jun-2024-

CP00.interface.yamlH A D06-Dec-20221.3 KiB5251

CRP0.interface.yamlH A D06-Dec-20221.8 KiB7271

DINF.interface.yamlH A D14-Mar-2022387 1615

LRP0.interface.yamlH A D14-Mar-2022470 2019

LRP1.interface.yamlH A D14-Mar-2022470 2019

LRP2.interface.yamlH A D14-Mar-2022470 2019

LRP3.interface.yamlH A D14-Mar-2022470 2019

LRP4.interface.yamlH A D14-Mar-2022470 2019

LRP5.interface.yamlH A D14-Mar-2022470 2019

LRP6.interface.yamlH A D14-Mar-2022470 2019

LRP7.interface.yamlH A D14-Mar-2022470 2019

LWP0.interface.yamlH A D14-Mar-20221.3 KiB5251

LWP1.interface.yamlH A D14-Mar-20221.3 KiB5251

LWP2.interface.yamlH A D14-Mar-20221.3 KiB5251

LWP3.interface.yamlH A D14-Mar-20221.3 KiB5251

LWP4.interface.yamlH A D14-Mar-20221.3 KiB5251

LWP5.interface.yamlH A D14-Mar-20221.3 KiB5251

LWP6.interface.yamlH A D14-Mar-20221.3 KiB5251

LWP7.interface.yamlH A D14-Mar-20221.3 KiB5251

LXR0.interface.yamlH A D14-Mar-2022391 1615

Location.interface.yamlH A D06-Dec-2022282 98

MER0.interface.yamlH A D14-Mar-2022346 1312

PSPD.interface.yamlH A D21-Feb-2023463 2019

README.mdH A D07-Jun-20241 KiB2317

UTIL.interface.yamlH A D14-Mar-20221.8 KiB8988

VCEN.interface.yamlH A D18-Jun-2024789 3231

VCFG.interface.yamlH A D14-Mar-2022480 2019

VEIR.interface.yamlH A D14-Mar-2022350 1312

VER0.interface.yamlH A D06-Dec-2022339 1312

VINI.interface.yamlH A D18-Jun-20242.1 KiB8684

VMPU.interface.yamlH A D14-Mar-2022582 2423

VMSC.interface.yamlH A D14-Mar-2022297 1211

VPRI.interface.yamlH A D14-Mar-2022497 2019

VR10.interface.yamlH A D18-Jun-2024530 2423

VRML.interface.yamlH A D09-Jun-2021721 3231

VRTN.interface.yamlH A D14-Mar-2022507 2019

VSBK.interface.yamlH A D27-Mar-20242.1 KiB9695

VSBP.interface.yamlH A D18-Jun-2024490 2019

VSRC.interface.yamlH A D14-Mar-2022393 1615

VSYS.interface.yamlH A D18-Jun-20241.5 KiB6463

VW10.interface.yamlH A D18-Jun-2024368 1615

VWML.interface.yamlH A D09-Jun-2021824 3635

README.md

1# IPZ VPD D-Bus Interfaces
2
3IPZ is a VPD (Vital Product Data) format used in IBM Power systems. The format
4consists of keywords that are stored as key-value pairs (Keyword name and its
5value). Keywords are grouped into records, usually with similar function grouped
6into a single record.
7
8The [OpenPower VPD][1] format is quite similar to the IPZ format and describes
9the record-keyword structure.
10
11Also refer to the [VPD Collection design document][2] that describes how the VPD
12collection application on the BMC will parse and publish the VPD data for IBM
13Power systems on D-Bus.
14
15The D-Bus interfaces defined here describe how IPZ VPD will be made available on
16D-Bus. Each YAML here represents a record in the IPZ VPD and keywords that
17belong to that record are represented as properties under that interface. The
18type of every property shall be a byte array.
19
20[1]:
21  https://www-355.ibm.com/systems/power/openpower/posting.xhtml?postingId=1D060729AC96891885257E1B0053BC95
22[2]: https://github.com/openbmc/docs/blob/master/designs/vpd-collection.md
23