Skip to content

Latest commit

 

History

History
110 lines (76 loc) · 4.78 KB

add_new_target.md

File metadata and controls

110 lines (76 loc) · 4.78 KB
Raw

Add new target

The power system device tree will maintain two types of targets (HWP's (Hardware Procedure) and Non-HWP's target) to represent hardware unit as target (node in device tree) based on needs to init and boot the POWER server. So, please refer respective subsection for steps.

  • To add hwp target, please refer here.

  • To add non-hwp target, please refer here.

  • To add target in the pdbg side, please refer here.

Note: The steps will point to many files and a few will be POWER10 specific so, please refer and update the respective files based on your requirement if you are looking for another POWER processor version.

HWP's Target

The target which is consumed by pub-ekb hardware procedure to init hardware units is called hwp target.

  1. Add corresponding mrw target id for required hwp's target type in hwp target name map list.

    Please refer here to get mrw target id value.

    # Format:- FAPITargetType:MRWTargetID

TARGET_TYPE_SYSTEM:sys-sys-power10

  2. Add the corresponding pdbg compatible property for the required mrw target id in pdbg compatible property list.

    Please refer here to get pdbg compatible property value.

    If the pdbg compatible property value is not found then, please refer here.

    # Format : MRWTargetID:PdbgCompatiblePropValue

unit-core-power10:ibm,power10-core

    Note: The pdbg compatible property map file will support more than one compatible property for the same mrw target id.

    E.g.: chip-processor-power10:"ibm,power-proc", "ibm,power10-proc"

  3. Add mrw target id into target filter list in new line.

  4. Add target name into class_map to read by using attribute tool.

Non-HWP's Target

The target which is consumed by the platform (openBMC apps and openPOWER Hostboot) to init and boot the POWER server is called non-hwp target.

  1. Add target definition in target definition xml file.

    Note:

    • target id should be same as mrw target id. Please refer here to get mrw target id value.

    • target should have parent tag.

    • target also can have non-hwps attributes information (please refer here to add if required).

      E.g.:

      <targetType>
   <attribute>
       <id>DISABLE_SECURITY</id>
   </attribute>
   <id>sys-sys-power10</id>
   <parent>sys</parent>
</targetType>

  2. Add corresponding pdbg compatible property for mrw target id in pdbg compatible property list.

    Please refer here to get pdbg compatible property value.

    If the pdbg compatible property value is not found then, please refer here.

    # Format : MRWTargetID:PdbgCompatiblePropValue

unit-core-power10:ibm,power10-core

    Note: The pdbg compatible property map file will support more than one compatible property for the same mrw target id.

    E.g.: chip-processor-power10:"ibm,power-proc", "ibm,power10-proc"

  3. Add mrw target id into target filter list in new line.

  4. Add target name into class_map to read by using attribute tool.

PDBG Target

The pdbg target need to be define in the pdbg to use a new target in the device tree.

  • Add a hardware unit in the pdbg side. please refer the sample.
  • Add a device tree node for the new target in the respective pdbg dts file. please refer the sample.

Note:

  • More samples.
  • These samples does not include the translation code to add in the hardware unit, that helps to perfom the scom operation on the new target.Please check any of the existing scomable targets code in the pdbg.