pseq: Update documentation

Update the phosphor-power-sequencer documentation to reflect recent
enhancements:
* New JSON configuration file format
* PowerSequencerDevice class hierarchy
* Enhanced pg

pseq: Update documentation

Update the phosphor-power-sequencer documentation to reflect recent
enhancements:
* New JSON configuration file format
* PowerSequencerDevice class hierarchy
* Enhanced pgood isolation support
* Automated tests

Change-Id: I8a7b76f4685cf9d55f1147658cc703b6d558f94b
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Remove deprecated files

Remove C++ and JSON files that are no longer needed by the
phosphor-power-sequencer application.

Over the past few months, several large enhancements have been
impleme

pseq: Remove deprecated files

Remove C++ and JSON files that are no longer needed by the
phosphor-power-sequencer application.

Over the past few months, several large enhancements have been
implemented in this application:
* New JSON file format that merges pin and rail elements, defines power
on sequence order of rails, defines PMBus PAGEs, and provides an
additional type of pgood fault checking based on output voltage.
* New pgood fault detection algorithm that is device independent, checks
rails in power on sequence order, ignores PAGEs that are not voltage
rails, and checks for faults using new output voltage method.
* New Device class hierarchy and Rail class that support automated
testing.

Remove the old C++ classes that are no longer used. Also remove the
configuration files that use the old JSON format.

Tested:
* Verified repository builds without errors
* Verified automated tests run without errors
* Verified application can successfully power the system on and off
without errors

Change-Id: I4473c01a30cfd898ffd11c75d537c2c3c95e945f
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Update STATUS_VOUT checks in config files

Update the phosphor-power-sequencer JSON configuration files for the
following systems:
* Rainier
* BlueRidge
* Everest
* Fuji

Add STATUS_VOUT checki

pseq: Update STATUS_VOUT checks in config files

Update the phosphor-power-sequencer JSON configuration files for the
following systems:
* Rainier
* BlueRidge
* Everest
* Fuji

Add STATUS_VOUT checking for voltage rails connected to digital monitors
(DMONs) on the UCD90320 power sequencer. Checking STATUS_VOUT is more
accurate than other methods in some scenarios.

Also remove STATUS_VOUT and READ_VOUT checking for the PSU rails on
Everest and Fuji. PMBus information is not available for the PSU rail
due to the way it is configured in the power sequencer device.

Change-Id: If5e630b2c17e0a34e240b1df512a9662a5370289
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Add config files for BlueRidge systems

Add phosphor-power-sequencer JSON configuration files for BlueRidge
systems.

Add config files in both the old and new JSON formats. The old format
will

pseq: Add config files for BlueRidge systems

Add phosphor-power-sequencer JSON configuration files for BlueRidge
systems.

Add config files in both the old and new JSON formats. The old format
will be removed soon, but that has not occurred yet.

Tested:
* Tested in simulation environment
* Verified BlueRidge JSON files present in
/usr/share/phosphor-power-sequencer directory in firmware image
* Verified old format BlueRidge JSON file was found and loaded
successfully
* Powered on chassis
* Verified powered on successfully and chassis pgood was true
* Verified no errors logged
* Verified phosphor-power-control did not write any errors to the
journal
* Powered off chassis
* Verified powered off successfully and chassis pgood was false
* Verified no errors logged
* Verified phosphor-power-control did not write any errors to the
journal

Change-Id: I92f8feb58557c3eabacbf3e9d7690c80c426b0a1
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Add config files for Fuji systems

Add phosphor-power-sequencer JSON configuration files for Fuji systems.

Add config files in both the old and new JSON formats. The old format
will be remove

pseq: Add config files for Fuji systems

Add phosphor-power-sequencer JSON configuration files for Fuji systems.

Add config files in both the old and new JSON formats. The old format
will be removed soon, but that has not occurred yet.

Tested:
* Tested in simulation environment
* Verified Fuji JSON files present in
/usr/share/phosphor-power-sequencer directory in firmware image
* Verified old format Fuji JSON file was found and loaded successfully
* Powered on chassis
* Verified powered on successfully and chassis pgood was true
* Verified no errors logged
* Verified phosphor-power-control did not write any errors to the
journal
* Powered off chassis
* Verified powered off successfully and chassis pgood was false
* Verified no errors logged
* Verified phosphor-power-control did not write any errors to the
journal

Change-Id: I739ca7d387af07fc0659d0e28ba366b01342a1b2
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Create Bonnell JSON cfg file in new format

Create an Bonnell JSON configuration file in the new format for the
phosphor-power-sequencer application.

The new JSON file format is documented in

pseq: Create Bonnell JSON cfg file in new format

Create an Bonnell JSON configuration file in the new format for the
phosphor-power-sequencer application.

The new JSON file format is documented in the
phosphor-power-sequencer/docs/config_file directory.

When all of the new C++ code and JSON config files are in place, the old
C++ code and JSON config files will be deleted.

Change-Id: I36b0b7b869d93016d0da2ef52397ca1f0244d3f9
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Create Everest JSON cfg file in new format

Create an Everest JSON configuration file in the new format for the
phosphor-power-sequencer application.

The new JSON file format is documented in

pseq: Create Everest JSON cfg file in new format

Create an Everest JSON configuration file in the new format for the
phosphor-power-sequencer application.

The new JSON file format is documented in the
phosphor-power-sequencer/docs/config_file directory.

When all of the new C++ code and JSON config files are in place, the old
C++ code and JSON config files will be deleted.

Change-Id: Id255ba3b6d99baf605aafa938e41dba239488dd4
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Create Rainier JSON config file in new format

Create a Rainier JSON configuration file in the new format for the
phosphor-power-sequencer application.

The new JSON file format is documented i

pseq: Create Rainier JSON config file in new format

Create a Rainier JSON configuration file in the new format for the
phosphor-power-sequencer application.

The new JSON file format is documented in the
phosphor-power-sequencer/docs/config_file directory.

When all of the new C++ code and JSON config files are in place, the old
C++ code and JSON config files will be deleted.

Change-Id: I15155f5d40e741f292fc2562bc3fddadcacbab7b
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Create Bonnell configuration file

Create the power sequencer configuration file for Bonnell systems. This
file identifies the PMBus rails and the GPIO lines/pins that should be
checked when a

pseq: Create Bonnell configuration file

Create the power sequencer configuration file for Bonnell systems. This
file identifies the PMBus rails and the GPIO lines/pins that should be
checked when a pgood failure occurs.

On Bonnell systems no GPIO lines need to be checked.

Tested:
* Configuration file loading
* Verified file is found on Bonnell systems using D-Bus property
* Verified file is loaded successfully without errors
* Verified all rails in file are stored in C++ data structures
* Verified having empty pin array does not cause an error
* Tested where file contains a syntax error
* Verified error message is written to journal
* Verified no error log created
* pgood detection
* Verified system powers on cleanly when no pgood error is present
* chassison
* Verified chassis is powered on
* Verified no error logs created
* Verified no error messages written to the journal
* poweron
* Verified system is powered on
* Verified no error logs created
* Verified no error messages written to the journal
* Verified system powers off cleanly when no pgood error is present
* chassisoff
* Verified chassis is powered off
* Verified no error logs created
* Verified no error messages written to the journal
* poweroff
* Verified system is powered off
* Verified no error logs created
* Verified no error messages written to the journal
* Test where a pgood error is detected in a rail
* Verified pgood failure is detected
* Verified error message written to the journal
* Verified GPIO values written to the journal
* Verified error log is created
* Tested with a pgood error on each rail in the config file
* Test where pgood failure occurs during power on attempt
* Test where pgood failure occurs after system was successfully
powered on

Change-Id: I431d2dd7e99f2a99bbab936d6fad03af5654886f
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Add support for UCD90160 device

Refactor power sequencer class hierarchy to add support for the UCD90160
device.

Tested:
* Verify UCD information is obtained successfully from EntityManager
*

pseq: Add support for UCD90160 device

Refactor power sequencer class hierarchy to add support for the UCD90160
device.

Tested:
* Verify UCD information is obtained successfully from EntityManager
* Verify JSON configuration file is found and parsed successfully
* Test where no pgood error occurs
* During power on
* Verify power on continues
* Verify no error is logged
* After chassis is powered on
* Verify chassis remains powered on
* Verify no error is logged
* Test where pgood error occurs
* During power on
* Verify power on stops and chassis is powered off
* Verify correct error is logged
* Verify callouts and additional data in error log are correct
* Detected via rail
* Detected via pin
* After chassis is powered on
* Verify chassis is powered off
* Verify correct error is logged
* Verify callouts and additional data in error log are correct
* Detected via rail
* Detected via pin

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: Ib00bc1ea34b504c245a4f0cb3979a86e51507f3c
Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com>

show more ...

pseq: Use more concise bracketing style in config

Per previous review suggestion and to improve readability, use a more
concise bracketing style in configuration files.

Signed-off-by: Jim Wright <j

pseq: Use more concise bracketing style in config

Per previous review suggestion and to improve readability, use a more
concise bracketing style in configuration files.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: I1dc8d97c7251eb49e8c13c71c4a33a67d315f7a0

show more ...

pseq: Fix backticks in README

Missing backticks in README Markdown files are causing improper
rendering. Fix them.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: Ibd49ae61a5188133d89b70

pseq: Fix backticks in README

Missing backticks in README Markdown files are causing improper
rendering. Fix them.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: Ibd49ae61a5188133d89b70cfb23af80f86d99670

show more ...

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

prettier: re-format

Prettier is enabled in openbmc-build-scripts on Markdown, JSON, and YAML
files to have consistent formatting for these file types. Re-run the
formatter on the whole repository.

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

show more ...

pseq: Add README for configuration file directory

Add a README markup file describing the contents and format of the
configuration file directory.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Ch

pseq: Add README for configuration file directory

Add a README markup file describing the contents and format of the
configuration file directory.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: I75f5b6cd52c54a7259d334ffe43c9dabbe452221

show more ...

pseq: Add presence checking

As a circumvention for hardware problems, it can be necessary to check
for device presence in order to prevent calling out not present
components. Add the ability to conf

pseq: Add presence checking

As a circumvention for hardware problems, it can be necessary to check
for device presence in order to prevent calling out not present
components. Add the ability to configure presence checking in the PSEQ
configuration files and use presence, when configured, in problem
determination.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: Ia9d8ee57f2d643f61ece45d9c03d523b891e98b8

show more ...

pseq: Add digital monitor rails to voltage fault

In order to provide better isolation prioritization and increase failure
data captured, add the digital monitor (dmon) rails to voltage fault
monitor

pseq: Add digital monitor rails to voltage fault

In order to provide better isolation prioritization and increase failure
data captured, add the digital monitor (dmon) rails to voltage fault
monitoring.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: I82dcee920044c083dd8c1a7c8fa24b6455143582

show more ...

pseq: Correct Everest system rail ordering

Everest system does not order rails in analog monitor (amon) pin order
as previous systems did and as initially assumed. Correct ordering per
additional cl

pseq: Correct Everest system rail ordering

Everest system does not order rails in analog monitor (amon) pin order
as previous systems did and as initially assumed. Correct ordering per
additional clarification from engineering.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: I772457cfca0d50f3567952128fa2742601a41f8b

show more ...

pseq: Cleanup Everest config file pin entries

In order to prevent incorrect isolation, remove from the Everest config
file the pins which do not factor into the overall chassis power good.

This com

pseq: Cleanup Everest config file pin entries

In order to prevent incorrect isolation, remove from the Everest config
file the pins which do not factor into the overall chassis power good.

This commit is the Everest version of
https://gerrit.openbmc-project.xyz/c/openbmc/phosphor-power/+/51249

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: Id3f818cadf09205a3d07a0f61fd1944ff835d795

show more ...

pseq: Remove disconnected Rainier system GPIO pins

Per engineering updates, remove disconnected GPIO pins from Rainier
configuration file. This will prevent incorrect isolation of power good
failure

pseq: Remove disconnected Rainier system GPIO pins

Per engineering updates, remove disconnected GPIO pins from Rainier
configuration file. This will prevent incorrect isolation of power good
failures.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: I6fe74d7bcde4474acc1c00171c7b4767b65b1eb1

show more ...

pseq: Cleanup Rainier config file pin entries

Remove from the Rainier config file the pins which do not factor into
the overall chassis power good. The PCIE slot pins do not represent a
power good f

pseq: Cleanup Rainier config file pin entries

Remove from the Rainier config file the pins which do not factor into
the overall chassis power good. The PCIE slot pins do not represent a
power good fail. The software pgood pin has been removed from current
system documentation. The individual PSU pgoods will be monitored by the
power supply application.

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: Id2ecb4eb2aee8048737a048b0ba45a1b48711334

show more ...

pseq: Add Everest configuration file

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: I2b456c098b7fcbfbf753e1745a7640418d50ed0d

pseq: Add Rainier configuration file

Signed-off-by: Jim Wright <jlwright@us.ibm.com>
Change-Id: Ib7caad4766bb80835c2cbe76a7854f5c48dae553