clang-format: re-format for clang-18

clang-format-18 isn't compatible with the clang-format-17 output, so we
need to reformat the code with the latest version. The way clang-18
handles lambda forma

clang-format: re-format for clang-18

clang-format-18 isn't compatible with the clang-format-17 output, so we
need to reformat the code with the latest version. The way clang-18
handles lambda formatting also changed, so we have made changes to the
organization default style format to better handle lambda formatting.

See I5e08687e696dd240402a2780158664b7113def0e for updated style.
See Iea0776aaa7edd483fa395e23de25ebf5a6288f71 for clang-18 enablement.

Change-Id: I299e3888aee418ddcf391a44cd9ba563edabfe83
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

Option to override dump request D-Bus path

Added option for overriding the object path for requesting OpenPOWER
dumps. On recent systems the object path is changed so adding option
to override the p

Option to override dump request D-Bus path

Added option for overriding the object path for requesting OpenPOWER
dumps. On recent systems the object path is changed so adding option
to override the path in the recipe.

Change-Id: Ice2f46e61b4a7604230d495463c5c90fdc549505
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>

show more ...

clang-format: copy latest and re-format

clang-format-17 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest

clang-format: copy latest and re-format

clang-format-17 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest .clang-format from the docs repository and reformat the
repository.

Change-Id: I06e9ad76b7e259a962f15f0b013d92a62f02a039
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

PHAL:Fix missing clock diagnostic data during ipl

During the IPL process, the Chassis Power State D-Bus property is
updated once all services and targets within the Chassis Power On target
have been

PHAL:Fix missing clock diagnostic data during ipl

During the IPL process, the Chassis Power State D-Bus property is
updated once all services and targets within the Chassis Power On target
have been completed. During this specific timeframe, when the
"op-clock-data-logger@.service.in" initiates, it may fail to capture
clock data due to a failed check. This situation occurs because, even
though the chassis power is turned on, the D-Bus property does not
provide the precise status, resulting in a missed opportunity to record
informational clock data.

The "op-clock-data-logger@.service.in" service is already configured to
start after the "obmc-host-started@%i.target" and is set to conflict
with the "obmc-host-stop@%i.target." This design ensures that whenever
this method is invoked, the chassis power will always be in the ON
state. Therefore, there is no need to redundantly check the chassis
power state for being ON. Consequently, the redundant conditional
statement has been removed.

Tested and found the clock informational diagnostic data added after
every ipl.

Change-Id: I56e62467be14c6f203d163d86aa6a5fd748d0d85
Signed-off-by: Deepa Karthikeyan <deepakala.karthikeyan@ibm.com>

show more ...

switch fmt::format to use std::format

fmt::format is supported in the c++ std. This will
help to remove fmt package dependency.

Change-Id: Ia3f5c607a348f062a0f112d5eae8b51ecc23fd37
Signed-off-by: J

switch fmt::format to use std::format

fmt::format is supported in the c++ std. This will
help to remove fmt package dependency.

Change-Id: Ia3f5c607a348f062a0f112d5eae8b51ecc23fd37
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>

show more ...

gcc13 : fix argument format issues

gcc13 based build failed with below error.
error: static assertion failed: Cannot format an argument.
To make type T formattable provide a formatter<T> special

gcc13 : fix argument format issues

gcc13 based build failed with below error.
error: static assertion failed: Cannot format an argument.
To make type T formattable provide a formatter<T> specialization:
https://fmt.dev/latest/api.html#udt

Problem looks similar to https://github.com/fmtlib/fmt/issues/391

Fix is to convert the "enum" type to underlying_type in fmt::format function.

Change-Id: I155fc854428492462dfec3b3818d08daa16e36bf
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>

show more ...

clang-format: copy latest and re-format

clang-format-16 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest

clang-format: copy latest and re-format

clang-format-16 has some backwards incompatible changes that require
additional settings for best compatibility and re-running the formatter.
Copy the latest .clang-format from the docs repository and reformat the
repository.

Change-Id: I66785e0aa71a93f9370db0168049cd62c1f69728
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>

show more ...

Change daily clock log to informational severity

The event log was using a severity of Error, and because the PEL message
registry had a severity of Informational, phosphor-log-manager would
spit ou

Change daily clock log to informational severity

The event log was using a severity of Error, and because the PEL message
registry had a severity of Informational, phosphor-log-manager would
spit out a trace about how the severities mismatched every time the PEL
was created.

Change-Id: Ia7559a5c3cfdf6ad93277783bfd85cb639af25a0
Signed-off-by: Matt Spinler <spinler@us.ibm.com>

show more ...

PHAL: Use fmt::join to log uint8_t array

Fix the compilation issue generated due to stricter type check
with in the library

Signed-off-by: Deepakala <deepakala.karthikeyan@ibm.com>
Change-Id: I25fc

PHAL: Use fmt::join to log uint8_t array

Fix the compilation issue generated due to stricter type check
with in the library

Signed-off-by: Deepakala <deepakala.karthikeyan@ibm.com>
Change-Id: I25fcd55c8a2fbd787ea1af57a7d4e5360c30b415

show more ...

PHAL: spare clock error callout priority update

Symbolic FRU REFCLOCK callout priority changed high->low in the
spare clock failure related PEL. This is based on RAS team input.

Tested:

"Primary S

PHAL: spare clock error callout priority update

Symbolic FRU REFCLOCK callout priority changed high->low in the
spare clock failure related PEL. This is based on RAS team input.

Tested:

"Primary SRC": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x3000",
"SRC Version": "0x02",
"SRC Format": "0x55",
"Virtual Progress SRC": "False",
"I5/OS Service Event Bit": "False",
"Hypervisor Dump Initiated":"False",
"Backplane CCIN": "2E33",
"Terminate FW Error": "False",
"Deconfigured": "False",
"Guarded": "False",
"Error Details": {
"Message": "Error during Spare clock initialisation"
},
"Valid Word Count": "0x09",
"Reference Code": "BD503009",
"Hex Word 2": "00080055",
"Hex Word 3": "2E330010",
"Hex Word 4": "00000000",
"Hex Word 5": "00000000",
"Hex Word 6": "00000000",
"Hex Word 7": "00000000",
"Hex Word 8": "00000000",
"Hex Word 9": "00000000",
"Callout Section": {
"Callout Count": "3",
"Callouts": [{
"FRU Type": "Normal Hardware FRU",
"Priority": "Mandatory, replace all with this type as a unit",
"Location Code": "U780C.ND0.WZS0003-P0",
"Part Number": "xxxx",
"CCIN": "xxxx",
"Serial Number": "xxxx"
}, {
"FRU Type": "Normal Hardware FRU",
"Priority": "Lowest priority replacement",
"Location Code": "U780C.ND0.WZS0003-P0-C61",
"Part Number": "xxxx",
"CCIN": "xxxx",
"Serial Number": "xxxx"
}, {
"FRU Type": "Symbolic FRU",
"Priority": "Lowest priority replacement",
"Part Number": "REFCLK0"
}]
}
}

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I991431c6b8794d6092e271e69d44bcf37c966508

show more ...

phal: Create PEL for empty guard file

Currently at the time of IPLing if the guard file is not present or
found empty, the IPLing terminates with an exception.

Added the new PEL "org.open_power.PHA

phal: Create PEL for empty guard file

Currently at the time of IPLing if the guard file is not present or
found empty, the IPLing terminates with an exception.

Added the new PEL "org.open_power.PHAL.Error.GuardPartitionAccess" to
address the above issue and continue to boot

Adding the IPL_ERR_GUARD_PARTITION_ACCESS enables us to generate the PEL
and "User Data 1" provides more information regarding the PEL

Tested:
Point to dummy file instead of actual guard file
Using the above error in the ipl callback, able to generate the below PEL
{
"0x50000E0C": {
"SRC": "BD8D300B",
"Message": "Guard partition access failure",
"PLID": "0x50000E0C",
"CreatorID": "BMC",
"Subsystem": "BMC Firmware",
"Commit Time": "10/06/2022 12:33:57",
"Sev": "Predictive Error",
"CompID": "0x3000"
}
}
...
},
"Callout Section": {
"Callout Count": "1",
"Callouts": [{
"FRU Type": "Maintenance Procedure Required",
"Priority": "Mandatory, replace all with this type as a
unit",
"Procedure": "BMC0001"
}]
}
},
...
"LOG013 2022-10-06 12:33:57": "Guard file
/var/lib/phosphor-software-manager/hostfw/running/NOFILE does not exist",
"_PID": "4393"
}

Signed-off-by: deepakala <deepakala.karthikeyan@ibm.com>
Change-Id: I07be6de35c9d5ce7b155e82fdcbc315a181d24c6

show more ...

PHAL: Added clock register data in the clock daily data logger

Informational log includes all the present clock register information
required for clock debug.

Tested:
"Clock0": "Functio

PHAL: Added clock register data in the clock daily data logger

Informational log includes all the present clock register information
required for clock debug.

Tested:
"Clock0": "Functional",
"Clock0 path": "/bmc0/i2c-0/oscrefclk0",
"Clock0_0x00": " 37 d0 40 03 00 bf 00 02",
"Clock0_0x08": " 01 00 00 00 00 00 21 0b",
"Clock0_0x10": " 17 12 01 00 30 24 04 72",
:: ::
"Clock0_0xe0": " 00 00 00 00 00 00 00 00",
"Clock0_0xe8": " 00 00 c1 00 00 00 00 00",
"Clock0_0xf0": " 00 00 00 00 00 00 00 00",
"Clock0_0xf8": " 00 00 00 00 00 00 00 00"

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: Ic536337f494febfa92162c0387cf2995e24e9b10

show more ...

PHAL: Added processor CFAM register data in the clock daily data logger

Informational log includes all the present processor CFAM register
information required for clock debug.

Tested:
"Proc0":

PHAL: Added processor CFAM register data in the clock daily data logger

Informational log includes all the present processor CFAM register
information required for clock debug.

Tested:
"Proc0": "Functional",
"Proc0 EC": "0x0000000020",
"Proc0 Location Code": "Ufcs-P0-C61",
"Proc0 REG 0x1007": "0x00200004",
"Proc0 REG 0x2804": "0x3c000020",
"Proc0 REG 0x2810": "0x80ff6007",
"Proc0 REG 0x2813": "0xefeeeeff",
"Proc0 REG 0x2814": "0x000000e4",
"Proc0 REG 0x2815": "0xc0000000",
"Proc0 REG 0x2816": "0xff000000",
"Proc0 REG 0x281d": "0x00000000",
"Proc0 REG 0x281e": "0x00000000",

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I47289a7c95ca9e64598eb26bbb5b49bf4fc2b680

show more ...

PHAL: clock daily data logger base infrastructure support

To support system clock issues debug added support to log clock
specific register information every 24 hours and report externally.

This co

PHAL: clock daily data logger base infrastructure support

To support system clock issues debug added support to log clock
specific register information every 24 hours and report externally.

This commit provides support to base infrastructure to log informational
logs every 24 hours and at the beginning of application start.

Tested:

"User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Log Committed by": "0x2000",
"Subsystem": "CEC Hardware - Clock",
"Event Scope": "Entire Platform",
"Event Severity": "Informational Event",
"Event Type": "Miscellaneous, Informational Only",
"Action Flags": [
"Service Action Required",
"Report Externally",
"HMC Call Home"
],
"Host Transmission": "Not Sent",
"HMC Transmission": "Not Sent"
},
"Primary SRC": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x3000",
"SRC Version": "0x02",
"SRC Format": "0x55",
"Virtual Progress SRC": "False",
"I5/OS Service Event Bit": "False",
"Hypervisor Dump Initiated":"False",
"Backplane CCIN": "2E33",
"Terminate FW Error": "False",
"Deconfigured": "False",
"Guarded": "False",
"Error Details": {
"Message": "Informational error to house clock debug info"
},
"Valid Word Count": "0x09",
"Reference Code": "BD58300A",
"Hex Word 2": "00080055",
"Hex Word 3": "2E330010",
"Hex Word 4": "00000000",
"Hex Word 5": "00000000",
"Hex Word 6": "00000000",
"Hex Word 7": "00000000",
"Hex Word 8": "00000000",
"Hex Word 9": "00000000"
}

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I91cffe17ffe7d38b1127f89e61484c597b9b378b

show more ...

sdbusplus: use shorter type aliases

The sdbusplus headers provide shortened aliases for many types.
Switch to using them to provide better code clarity and shorter
lines. Possible replacements are

sdbusplus: use shorter type aliases

The sdbusplus headers provide shortened aliases for many types.
Switch to using them to provide better code clarity and shorter
lines. Possible replacements are for:
* bus_t
* exception_t
* manager_t
* match_t
* message_t
* object_t
* slot_t

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I29672cb229bd07022b00f52105ac1d50ecacca62

show more ...

PHAL: Redundant mode clock error handling support

Added additional error support to handle clock failures callout
support for the spare clock supported system. In this case only
deconfigure clock ta

PHAL: Redundant mode clock error handling support

Added additional error support to handle clock failures callout
support for the spare clock supported system. In this case only
deconfigure clock target.

Tested: Clock test failure, with spare clock supported system

"User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Log Committed by": "0x2000",
"Subsystem": "CEC Hardware",
"Event Scope": "Entire Platform",
"Event Severity": "Informational Event",
"Event Type": "Miscellaneous, Informational Only",
"Action Flags": [
"Service Action Required",
"Report Externally",
"HMC Call Home"
],
"Host Transmission": "Not Sent",
"HMC Transmission": "Not Sent"
},

Primary SRC": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x3000",
"SRC Version": "0x02",
"SRC Format": "0x55",
"Virtual Progress SRC": "False",
"I5/OS Service Event Bit": "False",
"Hypervisor Dump Initiated":"False",
"Backplane CCIN": "2E33",
"Terminate FW Error": "False",
"Deconfigured": "False",
"Guarded": "False",
"Error Details": {
"Message": "Error during Spare clock initilaisation"
},
"Valid Word Count": "0x09",
"Reference Code": "BD503009",
"Hex Word 2": "00080055",
"Hex Word 3": "2E330010",
"Hex Word 4": "00000000",
"Hex Word 5": "00000000",
"Hex Word 6": "00000000",
"Hex Word 7": "00000000",
"Hex Word 8": "00000000",
"Hex Word 9": "00000000",
"Callout Section": {
"Callout Count": "1",
"Callouts": [{
"FRU Type": "Symbolic FRU",
"Priority": "Mandatory, replace all with this type as a unit",
"Part Number": "REFCLK0"
}]
}

"User Data 2": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",
"Data": [
{
"Deconfigured": true,
"EntityPath": [
35,
1,
0,
2,
0,
26,
1,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0,
0
],
"Priority": "H",
"SymbolicFRU": "REFCLK0"
}
]
}

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I553d5b7095ba6ea65fb9fa2c64188c05dbab936f

show more ...

Revert "PHAL: Additional callout support during sbe chipop timeout"

This reverts commit c3119d8e6b2ad3cb04b14fffedc0f73831d5300c.

Added support in PEL message registry to make the callout common.

Revert "PHAL: Additional callout support during sbe chipop timeout"

This reverts commit c3119d8e6b2ad3cb04b14fffedc0f73831d5300c.

Added support in PEL message registry to make the callout common.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I3fb2dfcbe956b798646388d62e930e1b87a34c73

show more ...

PHAL: Additional callout support during sbe chipop timeout

Sbe chip-op timeout case BMC should run sbe_extract_rc
procedure to identify the correct callout and service
action. Currently this procedu

PHAL: Additional callout support during sbe chipop timeout

Sbe chip-op timeout case BMC should run sbe_extract_rc
procedure to identify the correct callout and service
action. Currently this procedure based callout handling
is not place. Adding callout recommended by RAS team till
the actual callout code in place.

Tested:
"Callout Count": "2",
"Callouts": [{
"FRU Type": "Maintenance Procedure Required",
"Priority": "Mandatory, replace all with this type as a unit",
"Procedure": "BMC0002"
}, {
"FRU Type": "Normal Hardware FRU",
"Priority": "Medium Priority",
"Location Code": "xxx", --> processor callout
"Part Number": "xxx",
"CCIN": "xxx",
"Serial Number": "xxx"

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I13a16f314fe3a5e9eaeb3f84fdaa5bfe1924c7c4

show more ...

PHAL: Log Informational error for PEL created during poweroff

1)Log informational PELS in case system state is transitioning to
power-off for IPL procedures/hardware access failures

2) Don't add ca

PHAL: Log Informational error for PEL created during poweroff

1)Log informational PELS in case system state is transitioning to
power-off for IPL procedures/hardware access failures

2) Don't add callouts to PEL's created during transition to
power-off as the CEC will not be in expected state.

Tested: transition to poweroff
root@xxxbmc:/usr# peltool -lfh
{
"0x50003BEB": {
"SRC": "BD503001",
"Message": "Failure occurred during boot process",
"PLID": "0x50003BEB",
"CreatorID": "BMC",
"Subsystem": "CEC Hardware",
"Commit Time": "05/23/2022 13:57:53",
"Sev": "Informational Event",
"CompID": "0x3000"
}
}

root@xxxbmc:~# peltool -i 0x50003be0
{
"Private Header": {
"Section Version": "1",
"Sub-section type": "0",
"Created by": "0x3000",
"Created at": "05/23/2022 13:48:12",
"Committed at": "05/23/2022 13:48:12",
"Creator Subsystem": "BMC",
"CSSVER": "",
"Platform Log Id": "0x50003BE0",
"Entry Id": "0x50003BE0",
"BMC Event Log Id": "510"
},
"User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Log Committed by": "0x2000",
"Subsystem": "CEC Hardware",
"Event Scope": "Entire Platform",
"Event Severity": "Informational Event",
"Event Type": "Miscellaneous, Informational Only",
"Action Flags": [
"Event not customer viewable",
"Report Externally"
],
"Host Transmission": "Not Sent",
"HMC Transmission": "Not Sent"
},

.
.
.
Tested: transition to running
root@ever8bmc:/tmp# peltool -i 0x50003CF9
{
"Private Header": {
"Section Version": "1",
"Sub-section type": "0",
"Created by": "0x3000",
},
"User Header": {
"Section Version": "1",
"Sub-section type": "0",
"Log Committed by": "0x2000",
"Subsystem": "CEC Hardware",
"Event Scope": "Entire Platform",
"Event Severity": "Unrecoverable Error",
},

"User Data 0": {
"Created by": "0x2000",
"BMCState": "Ready",
"BootState": "Unspecified",
"ChassisState": "On",
"FW Version ID": "fw1020.00-57.7-2-gd86188a773",
"HostState": "TransitioningToRunning",
"Process Name": "/usr/bin/openpower-proc-control",
"System IM": "50003000"
},

Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
Change-Id: I078d5cba2e0fb705bf424d2f8f3010f2cd2063bb

show more ...

PHAL: Added non functional boot processor failure handling

Added support to create PELs' specific to non functional
boot processor related failure during boot window.

Implemented "NonFunctionalBoot

PHAL: Added non functional boot processor failure handling

Added support to create PELs' specific to non functional
boot processor related failure during boot window.

Implemented "NonFunctionalBootProc" message registry
specific PEL function and special callouts to these type
of failures.

Tested: verified PEL manually.

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I17c208197a9fd08b1a0aca519da4e03813862255

show more ...

PHAL: Add service dependency to DEVTREE creation

Start the services that require DEVTREE after the
openpower-update-bios-attr-table.service since that's the one that
sets up the DEVTREE symlink. Als

PHAL: Add service dependency to DEVTREE creation

Start the services that require DEVTREE after the
openpower-update-bios-attr-table.service since that's the one that
sets up the DEVTREE symlink. Also update the path to DEVTREE to the one
defined by the meson options.

Tested: Verified phal started after the bios attr service file, powered
on, and issued reboot at power on without any errors. Verified service
files had devtree path of:
Environment="PDBG_DTB=/media/hostfw/running/DEVTREE"

Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
Change-Id: If41f86b287b70c48d17c6f4b2af9aa0adfb81488

show more ...

PHAL: Additional callout support for sbe timeout error

Sbe Boot timeout or chip-op timeout case BMC should run
sbe_extract_rc procedure to identify the correct callout
and service action. Currently

PHAL: Additional callout support for sbe timeout error

Sbe Boot timeout or chip-op timeout case BMC should run
sbe_extract_rc procedure to identify the correct callout
and service action. Currently this procedure based callout
handling is not place. Adding callout recommended by RAS
team till the actual callout code in place.

Tested:

"Callout Count": "2",
"Callouts": [{
"FRU Type": "Maintenance Procedure Required",
"Priority": "Mandatory, replace all with this type as a unit",
"Procedure": "BMC0002"
}, {
"FRU Type": "Normal Hardware FRU",
"Priority": "Medium Priority",
"Location Code": "xxx", --> processor callout
"Part Number": "xxx",
"CCIN": "xxx",
"Serial Number": "xxx"

Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
Change-Id: I40444eb5da1a5f329b09dea1bce15e1bab53e1d8

show more ...

PHAL: Modify sbe error pel interface to pass in error type

At present all sbe related pels are created with severity
as Error(unrecoverable), modifying the API to specify the
severity type by the ca

PHAL: Modify sbe error pel interface to pass in error type

At present all sbe related pels are created with severity
as Error(unrecoverable), modifying the API to specify the
severity type by the caller.

Some of the chip-op is expected to fail in power-off/error path.
This commit will help to set custom priority of the failure.

Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
Change-Id: If072061bf995b2db58259eba64e7e8f7ace20f6c

show more ...

PHAL: Clock error handling support

-Supporting new flag to indicate planar callout required
-This flag can be set from either clock HWP error or clock
non-HWP error.
-Adding new error type

PHAL: Clock error handling support

-Supporting new flag to indicate planar callout required
-This flag can be set from either clock HWP error or clock
non-HWP error.
-Adding new error type for ipl error callback
-This error type can be called for non-hwp failures
-Additional data sent will be parsed and included in PEL
-Different prefix is added for HWP error and PLAT error.
Tested:
"Primary SRC": {
"Deconfigured": "False",
"Guarded": "False",
"Error Details": {
"Message": "Failure occured during boot process"
},
"Callout Section": {
"Callout Count": "1",
"Callouts": [{
"FRU Type": "Normal Hardware FRU",
"Priority": "Mandatory, replace all with this type as a unit",
"Location Code": "U780C.ND0.1234567-P0",
"Part Number": "F040221",
"CCIN": "2E33",
"Serial Number": "YL2E33010000"
}]
}
},
"User Data 1": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",

"PLAT_FFDC_FAIL_TYPE": "STATUS_READ",
"PLAT_FFDC_I2C_RC": "0",
"PLAT_HW_CO_01_CALLOUT_PLANAR": "true",
"PLAT_HW_CO_01_CLK_POS": "1",
"PLAT_HW_CO_01_HW_ID": "PROC_REF_CLOCK",
"PLAT_HW_CO_01_PRIORITY": "HIGH",
"PLAT_RC": "10",
"PLAT_RC_DESC": "Error in executing clock initialisation",
"_PID": "21916"
},
"User Data 2": {
"Section Version": "1",
"Sub-section type": "1",
"Created by": "0x2000",
"Data": [
{
"Deconfigured": false,
"Guarded": false,
"InventoryPath": "/xyz/openbmc_project/inventory/system/chassis/motherboard",
"Priority": "H"
}
]
}

Signed-off-by: Rajees P P <rajerpp1@in.ibm.com>
Change-Id: Ifd2268b1c99be4dbfa9234e910d7e87771adb176

show more ...

PHAL: Fixing wrong callout of reference target

-The target provided in HwCallout structure is, only a reference target
to find the actual hardware target need to be called out. So, this
target sho

PHAL: Fixing wrong callout of reference target

-The target provided in HwCallout structure is, only a reference target
to find the actual hardware target need to be called out. So, this
target should not be called out.

Signed-off-by: Rajees P P <rajerpp1@in.ibm.com>
Change-Id: I64082ae30d936d8b2e46458b460e66ff064f049b

show more ...