| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Feedback from the field shows it would be useful to
have information about the sensors that are too high
or low in the metadata rather than the type.
This is a free format metadata string field so that
the code that creates this error can put in whatever
metadata it thinks is necessary, ideally including
information about the sensor(s) in question.
Tested: Built repository
Change-Id: I6f790a314d132bfbdc45c90a13f9c3831163c2f1
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This interface should be instantiated for the phosphor::events
namespace.
Currently Event interface and Entry Interface has common
properties but the plan is to split the Entry interface into
Event and Entry specific properties.
Will do it later with github issue
https://github.com/openbmc/openbmc/issues/2923
Change-Id: Ic84ea85d20126473e2723e4868c685f0a9d298e0
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
|
|
|
| |
Change-Id: I54222ac9c6f1877b7786d4a3c35aaae526844ff8
Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
|
|
|
|
|
|
|
|
|
|
| |
To be able to correctly tell an error has occurred, as
well as to be able to dynamically create sensor scaling
factors the MaxValue and MinValue interface need to be added.
This commit adds these to the interface.
Change-Id: I8f0abfa3446350329c38210beb540faddc0a65a0
Signed-off-by: James Feist <james.feist@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The IPMI spec defines actions which can be set at runtime that define
what action the watchdog will take when it expires. With this change our
watchdog daemon can be dynamically reconfigured to execute a target that
maps to the defined action.
The current list of actions maps directly from the IPMI spec. We don't
require that the list strictly adheres to the list in the spec, but this
is a good starting point since they are generic host actions. A commit
to phosphor-watchog will accompany this change in order to respect the
actions defined in this interface. This change defaults the action to
HardReset, which will ensure the behavior is consistent with previous
behavior regardless of updating the phosphor-host-ipmid.
Change-Id: I7b293394326652b292b4bd23950a7f947ece8306
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding an initialization value to the dbus api allows the host ipmi
daemon or any other user of the host watchdog api to determine if they
have already initialized the host watchdog without keeping any of their
own state. This is useful for being able to report a not initialized error
to the host system when it makes a watchdog reset call. Since this value
is defined by default as false, whenever the watchdog daemon restarts
and loses state the host will be able to see that it has not yet been
initialized. The host can then reinitialize the watchdog if implemented
according to the spec. As this value is inteded purely for state tracking
on the client side, the server does not need to modify or even read this value.
Change-Id: I224995fdb09fcf21ba729dbd88e41a31e82eacad
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
|
|
|
|
|
|
| |
Added the PowerSupplyRedundancy interface to be used to set the
redundancy of the power supplies.
Change-Id: I5394975963b79ae74ed7a6caf7a5bf48879f34ba
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you build phosphor-dbus-interfaces against an sdbusplus that resides
in a non-standard include location the configure system should still be able
to locate the headers based on the pkg-config information. Since
AC_CHECK_HEADERS uses the CPPFLAGS variable when calling `cpp` to check for
headers, we need to temporarily add the CFLAGS provide by the sdbusplus module.
This populates CPPFLAGS with the include prefixes necessary to find the
headers for sdpbusplus.
Change-Id: I1e3fc50daf5aa5e3025441d469db20fcc0f7f0b4
Signed-off-by: William A. Kennington III <wak@google.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following reference indicates that pwm[n], when available
are consistently implemented. Therefore, it's a valid approach.
https://www.kernel.org/doc/Documentation/hwmon/sysfs-interface
I'd like to use this interface with phosphor-hwmon to control our
fans in a similar fashion to RPM-driven control via a target.
Change-Id: Ic1d9363d616e650ba7d5162f424700d6768cdf1f
Signed-off-by: Patrick Venture <venture@google.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
I believe this is the only possible way we can realistically
provide forwards and backwards API compatibility.
We have existing API users, and we can't go and rewrite the world,
so we need to extend the API in a way that enables them to continue
working.
Change-Id: I741485adf98126919b2a521d8bfbd235b13750ae
Signed-off-by: Stewart Smith <stewart@linux.vnet.ibm.com>
|
|
|
|
|
|
|
| |
Resolves openbmc/openbmc#2691
Change-Id: I95d76f39a66b3d88af050584fde2ff277881c76a
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
|
|
|
|
|
|
|
|
|
| |
Add assertion made in https://gerrit.openbmc-project.xyz/#/c/8086/
- enclosure_identify has the special property that it is routed
from the ipmi command chassis identify.
Change-Id: Ic9a5d46b9ff2235f8a197e4ca4e4797d1bf72ce8
Signed-off-by: James Feist <james.feist@linux.intel.com>
|
|
|
|
|
|
|
|
|
| |
The Scale and Unit fields are immutable, they can't change
for a sensor. This is to enable pre-configuring the Scale or
Unit in the phosphor-host-ipmid YAML.
Change-Id: I36d0567a04687146defc70d2e4dcd3444653f4fe
Signed-off-by: Patrick Venture <venture@google.com>
|
|
|
|
|
|
|
|
|
|
|
| |
It's the choice of the implementer on whether to apply the
policy on just a power loss or on a power loss and a BMC
reboot
Partially Resolves openbmc/openbmc#2454
Change-Id: Ia52a92a23d8e66f667a2c7d6ca163ae78915232f
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
|
|
|
| |
To be used when we shutdown the system due to not enough
present or functional fans.
Change-Id: I3a30592cba767e8fbbcba4286df1c62940eaba9e
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
|
|
|
| |
PCI Initialization is missing in the list of boot progress
stages, adding that to the boot progress interface yaml
Change-Id: I6fe563ac89a33b2fe06006bbe0ddf206d5d61de3
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Prior commit added xyz.openbmc_project.Common.Device.ReadFailure
and xyz.openbmc_project.Common.Device.WriteFailure but did not
have enough documentation.
This commit adds documentation on how to interpret that error
Change-Id: I627b44ba7d4e3d0adc9f2b7362afbe470d8467bc
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
|
|
|
| |
Change-Id: I9adc3ae2d0e2a8b89b8d7f00c7f558f329680298
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
|
|
|
| |
Change-Id: I0e67d6b6a476ac6212d53fbdfd7efc3e9c06f7ab
Signed-off-by: Patrick Venture <venture@google.com>
|
|
|
|
|
|
|
|
|
| |
This commit creates Common device error yaml defining
Read and Write failures, that can be used by any application
getting any read / write failures doing device operation
Change-Id: I75c07ae2a2f8622065cb8522af534a71487bced9
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds a README explanation of the FactoryReset interface,
both in generic terms and a brief description of each of the current
implementations. This is intended to clarify what does and doesn't
occur when each factory reset implementation is called.
Resolves openbmc/openbmc#2229
Change-Id: Ic5072346dbe9bb87af05192de19ed17be2bb1482
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the event that one of the factory reset functions fails, we need to
create an error indicating that to the error log. This commit extends
the factory reset interface with the InternalFailure error for that
purpose.
Resolves openbmc/openbmc#1721
Change-Id: Ieefa0330d78aa8e6b7d344e4d6b8b067fdb8a7c8
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
|
|
|
|
|
|
|
|
|
| |
This error will be used on Witherspoon when the power
sequencer chip detects a power fault, which requires
a power off to be done.
Change-Id: Ia5f99c67c4e9436ca86f9d94d08644fcac012824
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Will be used on Witherspoon when the GPUs report an overtemp
to the power sequencer chip. The failing GPU will be called
out in a separate overtemp error log, and then this shutdown
error will be created when code powers off the system to
protect the chip.
Change-Id: I55b836f469f0fc035386130a16b433a5eba96a8b
Signed-off-by: Matt Spinler <spinler@us.ibm.com>
|
|
|
|
|
|
|
|
| |
Created Processor ThermalEvent Shutdown Error.
To used as part of openbmc/openbmc#2190.
Change-Id: I2441a4eb69df36a1dbf623579c5e3bf5c6a818ae
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
| |
Change-Id: I9b23ebcae15e1feee0eb32c42b184c8a429e0977
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
|
|
|
|
|
| |
The interface has a single method now called 'DeleteAll'.
Change-Id: Ifd4d4046f614dfbe622adb5820bceae2847bdec8
Signed-off-by: Nagaraju Goruganti <ngorugan@in.ibm.com>
|
|
|
|
|
|
|
|
| |
Add type-only interfaces for ethernet card, chassis
and system/enclosure.
Change-Id: I347b34790dfc1b0d09c7c6dba9a6950b62d433c0
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The interface consists of a boolean property called 'Enabled'. Setting
that to true or false helps determine whether an object implementing
this interface is usable or not.
This will help users to select an object from a collection of similar
objects. For instance, given these objects : setting/permanent/boot and
setting/one-time/boot, one or both of these objects could implement the
Enable interface to allow a user to state how the boot setting should be
applied - the next boot versus all subsequent boots.
Change-Id: I35df5384d459ba7d6cd9afab630f145b5a5c9948
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
|
|
|
|
|
| |
Change-Id: I93764fc9c8e6f05d41ece7a6605452bbbac11c3b
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
|
|
| |
Added Sensor Threshold CriticalHigh and CriticalLow errors.
Change-Id: Ie29a39ed5c58e51a38c33952e582de1b35811247
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
| |
Change-Id: Ia0da0d12b967b80d0ef3800146de01033e425613
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
|
|
|
|
|
|
|
|
| |
Created an Common Interface UUID with property
name UUID.
Change-Id: Ic1b5928c6cd330f9d88929810ee5c422221e100f
Signed-off-by: Dinesh Chinari <chinari@us.ibm.com>
|
|
|
|
|
| |
Change-Id: Ie9451b2b67a281e9d5eac47d3d06e4ea6f0e2323
Signed-off-by: Michael Tritz <mtritz@us.ibm.com>
|
|
|
|
|
| |
Change-Id: I409066f2bc1232e48e5693a177d39859ba6ec84d
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Added NotPresent and Nonfunctional inventory errors.
An example of this being used is to log an error when
a power supply is removed in Witherspoon.
In Witherspoon, both power supplies are needed
to power all 6 GPUs.
Change-Id: I086c2de8e0c44c941c527c44af022c8c440d70f4
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Add a framework for describing minimum ship level configurations.
Minimum ship level configurations could be useful to enable legacy
hardware configurations in product development while still preventing
manufacturing escapes of those legacy parts.
Change-Id: I005a035ac824a3f966caee4582f0e3344cfa0bca
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
|
|
|
| |
Change-Id: I244484a4dcac0b01fb859a9d5436c3f0bb04b39d
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
|
|
|
|
|
| |
Change-Id: I4274d9df94d62ec58e1e6beb95db81754856890e
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
|
|
|
|
|
| |
Change-Id: I46ccac9e3e68f3b505885667aca9cc80c847aa63
Signed-off-by: Tom Joseph <tomjoseph@in.ibm.com>
|
|
|
|
|
| |
Change-Id: Ia2a7b51539f00be4af59f09bd8ccac582d9ea983
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
|
|
|
|
|
|
| |
This property will be used to enable and disable the
power cap for the system
Change-Id: Ifd7b2be89a33e45b9ed2e3832aa13d81b829bc85
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
|
|
| |
Resolves openbmc/openbmc#1685
Change-Id: I24e3b9757eed523240c65823952c4dcee24f329d
Signed-off-by: Ratan Gupta <ratagupt@in.ibm.com>
|
|
|
|
|
| |
Change-Id: I0d26e8e3e06eb72c92e9410cb83b3b20c464c303
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
|
|
|
|
|
| |
Change-Id: Ic52faba7a24bcf58f3326b1587282ca8398e9a70
Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
|
|
|
|
|
|
|
|
| |
A/C will not be preserved on host reboot requests, there's
no need to include that detail in the interface anyway
Change-Id: If3d33cea8c492191f0dfd58bfcfd99bfe9f9baee
Signed-off-by: Andrew Geissler <andrewg@us.ibm.com>
|
|
|
|
|
|
|
|
|
|
| |
Initial thought behind watchdog implementation was that when
the timer expires, it would broadcast a signal. A better design
was thought of in the meantime and that would call into a
user requested target post timer expiration.
Change-Id: Ibe148ed5cd0e8d72949324f64c87704a8e9e7236
Signed-off-by: Vishwanatha Subbanna <vishwa@linux.vnet.ibm.com>
|
|
|
|
|
| |
Change-Id: I7cf363917f7d21664cd60433f23335b94f095147
Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com>
|
|
|
|
|
|
|
|
| |
Formatted the headings of the Network README file and fixed the
formatting that caused the eg. endpoints to not render correctly on the webpage.
Change-Id: I32863a668b9bba03f4a95eb762ad7d7203b7a601
Signed-off-by: Victor Hu <whowutwut@gmail.com>
|
|
|
|
|
|
|
| |
Resolves openbmc/openbmc#1486.
Change-Id: I377f40516a6a0317bb4b5d811704288048c83cc8
Signed-off-by: Deepak Kodihalli <dkodihal@in.ibm.com>
|