commit 13efee8e32bbb494f859d117f32b09ee30119894
author Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> Thu Feb 01 21:47:29 2024 -0600
committer Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com> Fri Feb 02 07:07:36 2024 +0000
tree f336d0fca6525e97cc9887cde91bc521bdc68a09
parent 2cb6769e0c07860baba569dcf194b9479d54364b

Everest: Fix MUX configuration

Fix the MUX configuration to correctly point to the device i2c

Change-Id: Icb89bc94f82cb286a85a89cf8ab20c4f8e414bc1
Signed-off-by: Jinu Joy Thomas <jinu.joy.thomas@in.ibm.com>

README.md

diff --git a/README.md b/README.md
index f29880e..134ec1c 100644
--- a/README.md
+++ b/README.md
@@ -28,7 +28,7 @@
 
 - It parses all the records and keywords from the VPD, including large keywords
   (Keywords that begin with a `#` and are > 255 bytes in length).
-- It relies on a runtime JSON configuration (see examples/inventory.json) to
+- It relies on a runtime JSON configuration (see examples/inventory.json) tocf
   determine the D-Bus object path(s) that hold interfaces and properties
   representing the VPD for a given VPD file path.
 
@@ -38,10 +38,10 @@
 
 ## TODOs and Future Improvements
 
-1.  The long-term goal is to completely do away with the build time YAML driven
-    configurations and instead reconcile the OpenPower VPD parser and the IBM
-    VPD parser applications into a single runtime JSON driven application.
-2.  Add details to the README on how to configure and build the application.
-3.  More JSON documentation.
-4.  Support for more IBM VPD formats.
-5.  VPD Write and tool documentation.
+1. The long-term goal is to completely do away with the build time YAML driven
+   configurations and instead reconcile the OpenPower VPD parser and the IBM VPD
+   parser applications into a single runtime JSON driven application.
+2. Add details to the README on how to configure and build the application.
+3. More JSON documentation.
+4. Support for more IBM VPD formats.
+5. VPD Write and tool documentation.

config/ibm/50003000.json

diff --git a/config/ibm/50003000.json b/config/ibm/50003000.json
index af46a95..2d39773 100644
--- a/config/ibm/50003000.json
+++ b/config/ibm/50003000.json
@@ -24,6 +24,23 @@
             }
         }
     },
+    "muxes": [
+        {
+            "i2bus": "4",
+            "deviceaddress": "0xE0",
+            "holdidlepath": "/sys/bus/i2c/drivers/pca954x/4-0070/hold_idle"
+        },
+        {
+            "i2bus": "5",
+            "deviceaddress": "0xE0",
+            "holdidlepath": "/sys/bus/i2c/drivers/pca954x/5-0070/hold_idle"
+        },
+        {
+            "i2bus": "6",
+            "deviceaddress": "0xE0",
+            "holdidlepath": "/sys/bus/i2c/drivers/pca954x/6-0070/hold_idle"
+        }
+    ],
     "frus": {
         "/sys/bus/i2c/drivers/at24/8-0050/eeprom": [
             {

config/ibm/50003000_v2.json

diff --git a/config/ibm/50003000_v2.json b/config/ibm/50003000_v2.json
index 71049eb..9e66e2f 100644
--- a/config/ibm/50003000_v2.json
+++ b/config/ibm/50003000_v2.json
@@ -26,6 +26,11 @@
     },
     "muxes": [
         {
+            "i2bus": "4",
+            "deviceaddress": "0xE0",
+            "holdidlepath": "/sys/bus/i2c/drivers/pca954x/4-0070/hold_idle"
+        },
+        {
             "i2bus": "5",
             "deviceaddress": "0xE0",
             "holdidlepath": "/sys/bus/i2c/drivers/pca954x/5-0070/hold_idle"
@@ -34,11 +39,6 @@
             "i2bus": "6",
             "deviceaddress": "0xE0",
             "holdidlepath": "/sys/bus/i2c/drivers/pca954x/6-0070/hold_idle"
-        },
-        {
-            "i2bus": "7",
-            "deviceaddress": "0xE0",
-            "holdidlepath": "/sys/bus/i2c/drivers/pca954x/7-0070/hold_idle"
         }
     ],
     "frus": {