ocmb target support in system device tree for ocmb scom

RameshIyyar commented 4 years ago

Change index property value for ocmb target based on parent omi target CHIP_UNIT attribute value.
Update ocmb target node name as ocmbX (X - instance id)
Add required compatible property "ibm,power-ocmb" to ocmb for scom operation

RameshIyyar commented 4 years ago

Update index property value for OCMB target OCMB target index property value should be local scope within proc target for scom operation but ocmb target is not pervasive targets and it does not have CHIP_UNIT attribute so, using OMI target CHIP_UNIT attribute value as index property value for ocmb target.
Change ocmb target node name Currently, All targets node name are picked from PHYS_PATH value i.e considered least target path element from PHYS_PATH attibute value. For example to proc target, If value is "physical:sys-0/node-0/proc-0" then "proc-0" picked and removed "-" from that element value. Similarly, ocmb target name will be "ocmb_chip0" but, pdbg expecting as "ocmb0" i.e without "_chip" to make generic for scom operation so, change ocmb target node name as per pdbg expectation.
Update ocmb compatible property The pdbg expecting ocmb target compatible property value as "ibm,power-ocmb" for scom operation so, need to add same value into ocmb compatible property list i.e it will support both "ibm,power-ocmb" and "ibm,power10-ocmb" values.

ojayanth commented 4 years ago

@RameshIyyar please include PR information.

RameshIyyar commented 4 years ago

Above story points are addressed and merged into phal/pdata Ref: https://github.ibm.com/phal/pdata/pull/25

ibm-openbmc / dev