From d209622b9f3e12e8197992c561851824ba1f39c8 Mon Sep 17 00:00:00 2001 From: Dan Daly Date: Tue, 13 Feb 2024 09:36:09 -0800 Subject: [PATCH 1/4] docs: updated BMC section with PLDM details Signed-off-by: Dan Daly --- OPI_DEVICE_PROV_LIFE.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/OPI_DEVICE_PROV_LIFE.md b/OPI_DEVICE_PROV_LIFE.md index 3e4c450..4c0f753 100644 --- a/OPI_DEVICE_PROV_LIFE.md +++ b/OPI_DEVICE_PROV_LIFE.md @@ -19,10 +19,10 @@ For the purposes of this specification a 'device' is a PCI device that intends t ## BMC Connectivity Baseline -- **PLDM Type 2 (Monitoring & Control)**: Device shall support DMTF PLDM type 2 sensors using a standard PCIe connector physical medium MCTP transport (e.g. SMBus, PCIe VDM, USB).  This includes the ability to read and monitor in addition to being able to set thresholds for: - - Temperature Sensors SHALL be supported - - Voltage Sensors SHALL be supported -- **Identification**: Devices shall identify themselves to the BMC with the equivalent of the QR code for use in sZTP. +1. **PLDM**: Device shall support DMTF Platform Level Data Model (PLDM) type 2 (Monitoring & Control) using a standard PCIe connector physical medium MCTP transport (e.g. SMBus, PCIe VDM, USB). This includes the ability to read and monitor in addition to being able to set thresholds. PLDM is used to support get the following information from the device: + 1. **Temperature**: Temperature sensors shall be supported + 2. **Power**: Voltage sensors shall be supported + 3. **Identification (via a File)**: The File Transfer specification is targeting ratification and release by the DMTF in the first half of 2024. This specification provides a standards based mechanism by which the BMC may perform File I/O operations on a device. In this instance the IPU/DPU shall provide a 'file' which can be read by the BMC that has a well defined name and format. The contents of the file will contain the necessary information to identify the IPU/DPU - the same information provided by a QR code on the physical device. ## Life Cycle Management From fca7f746cc711fc67f268ae8c42f14f8a10a20b0 Mon Sep 17 00:00:00 2001 From: Dan Daly Date: Tue, 13 Feb 2024 09:39:34 -0800 Subject: [PATCH 2/4] docs: updated BMC section with PLDM details format1 Signed-off-by: Dan Daly --- OPI_DEVICE_PROV_LIFE.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/OPI_DEVICE_PROV_LIFE.md b/OPI_DEVICE_PROV_LIFE.md index 4c0f753..7477703 100644 --- a/OPI_DEVICE_PROV_LIFE.md +++ b/OPI_DEVICE_PROV_LIFE.md @@ -20,9 +20,9 @@ For the purposes of this specification a 'device' is a PCI device that intends t ## BMC Connectivity Baseline 1. **PLDM**: Device shall support DMTF Platform Level Data Model (PLDM) type 2 (Monitoring & Control) using a standard PCIe connector physical medium MCTP transport (e.g. SMBus, PCIe VDM, USB). This includes the ability to read and monitor in addition to being able to set thresholds. PLDM is used to support get the following information from the device: - 1. **Temperature**: Temperature sensors shall be supported - 2. **Power**: Voltage sensors shall be supported - 3. **Identification (via a File)**: The File Transfer specification is targeting ratification and release by the DMTF in the first half of 2024. This specification provides a standards based mechanism by which the BMC may perform File I/O operations on a device. In this instance the IPU/DPU shall provide a 'file' which can be read by the BMC that has a well defined name and format. The contents of the file will contain the necessary information to identify the IPU/DPU - the same information provided by a QR code on the physical device. + 1. **Temperature**: Temperature sensors shall be supported + 2. **Power**: Voltage sensors shall be supported + 3. **Identification (via a File)**: The File Transfer specification is targeting ratification and release by the DMTF in the first half of 2024. This specification provides a standards based mechanism by which the BMC may perform File I/O operations on a device. In this instance the IPU/DPU shall provide a 'file' which can be read by the BMC that has a well defined name and format. The contents of the file will contain the necessary information to identify the IPU/DPU - the same information provided by a QR code on the physical device. ## Life Cycle Management From bec17dee8c036177d85d78914b4955564f17ebc6 Mon Sep 17 00:00:00 2001 From: Dan Daly Date: Tue, 13 Feb 2024 11:21:35 -0800 Subject: [PATCH 3/4] docs: updated BMC section with PLDM details including FRU Signed-off-by: Dan Daly --- OPI_DEVICE_PROV_LIFE.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/OPI_DEVICE_PROV_LIFE.md b/OPI_DEVICE_PROV_LIFE.md index 7477703..b3cde18 100644 --- a/OPI_DEVICE_PROV_LIFE.md +++ b/OPI_DEVICE_PROV_LIFE.md @@ -22,7 +22,12 @@ For the purposes of this specification a 'device' is a PCI device that intends t 1. **PLDM**: Device shall support DMTF Platform Level Data Model (PLDM) type 2 (Monitoring & Control) using a standard PCIe connector physical medium MCTP transport (e.g. SMBus, PCIe VDM, USB). This includes the ability to read and monitor in addition to being able to set thresholds. PLDM is used to support get the following information from the device: 1. **Temperature**: Temperature sensors shall be supported 2. **Power**: Voltage sensors shall be supported - 3. **Identification (via a File)**: The File Transfer specification is targeting ratification and release by the DMTF in the first half of 2024. This specification provides a standards based mechanism by which the BMC may perform File I/O operations on a device. In this instance the IPU/DPU shall provide a 'file' which can be read by the BMC that has a well defined name and format. The contents of the file will contain the necessary information to identify the IPU/DPU - the same information provided by a QR code on the physical device. + 3. **Identification (via FRU)**: The Following fields are defined by [DSP0257](https://www.dmtf.org/sites/default/files/standards/documents/DSP0257_1.0.0.pdf) - 212 (General FRU Record): + 1. **Type, Model, Part Number**: Used to identify the type, model, and part number for this device + 2. **Serial Number**: Used to identify this particular device + 3. **Manufacturer, Manufacturer Date, Vendor, Name, SKU**: Used to identfy the manufacturer including the SKU + 4. **Version**: The hardware version of this device + 5. **Asset Tag**: The same information provided by a QR code on the physical device. ## Life Cycle Management From 27b04d17269438a96081c7b22db8398b2f35c764 Mon Sep 17 00:00:00 2001 From: Dan Daly Date: Tue, 13 Feb 2024 11:22:58 -0800 Subject: [PATCH 4/4] docs: updated BMC section with PLDM details including FRU linter fixes Signed-off-by: Dan Daly --- OPI_DEVICE_PROV_LIFE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/OPI_DEVICE_PROV_LIFE.md b/OPI_DEVICE_PROV_LIFE.md index b3cde18..85a2a33 100644 --- a/OPI_DEVICE_PROV_LIFE.md +++ b/OPI_DEVICE_PROV_LIFE.md @@ -24,7 +24,7 @@ For the purposes of this specification a 'device' is a PCI device that intends t 2. **Power**: Voltage sensors shall be supported 3. **Identification (via FRU)**: The Following fields are defined by [DSP0257](https://www.dmtf.org/sites/default/files/standards/documents/DSP0257_1.0.0.pdf) - 212 (General FRU Record): 1. **Type, Model, Part Number**: Used to identify the type, model, and part number for this device - 2. **Serial Number**: Used to identify this particular device + 2. **Serial Number**: Used to identify this particular device 3. **Manufacturer, Manufacturer Date, Vendor, Name, SKU**: Used to identfy the manufacturer including the SKU 4. **Version**: The hardware version of this device 5. **Asset Tag**: The same information provided by a QR code on the physical device.