phosphor-dbus-interfaces, branch master

Add frequency sensor to YAML

2018-05-19T09:42:50+00:00

Add PowerOnHours interface

2018-04-04T10:17:15+00:00

PowerOnHours interface to tell how many hours the system has been powered-on. Partially Resolves openbmc/openbmc#2979 Change-Id: I61b149e38717a389f57c2d881ced7faf823d25a7 Signed-off-by: Nagaraju Goruganti

Add information about functional association

2018-03-07T11:19:04+00:00

Added a line about the functional association. There is much more about the functional association at github.com/openbmc/docs/blob/master/code-update/ubi-code-update.md#associations but thought it was good to add a line in the Software interface README. Change-Id: Ibf172d15ead248bff679eb45886a0ee182612a55 Signed-off-by: Gunnar Mills

Create State.Boot.Raw interface

2018-03-06T14:09:25+00:00

Provide an interface for broadcasting POST codes on the dbus. This allows one consumer on the device while allowing anyone listening to receive the data and perform an action. Change-Id: I3c7bf6afb77be7ce49198e394547ddf8d9153de6 Signed-off-by: Patrick Venture

Add TurboAllowed interface

2018-03-01T14:04:49+00:00

TurboAllowed interface is used to tell host that it is allowed to turn on turbo mode. Turbo mode is a setting to enable processor frequency boosting. Change-Id: I85fe32de9777580d9feaab5ae22e6db6a2e691ff Signed-off-by: Jayanth Othayoth

Change metadata on Critical high/low sensor errors

2018-02-27T13:53:48+00:00

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

Logging: Create the new event interface.

2018-02-21T14:15:31+00:00

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

Network: Add property:SendHostNameEnabled in DHCP Configuration

2018-02-14T21:31:48+00:00

Change-Id: I54222ac9c6f1877b7786d4a3c35aaae526844ff8 Signed-off-by: Nagaraju Goruganti

Add MaxValue and MinValue interface to Sensors

2018-02-14T21:29:29+00:00

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

watchdog: Support setting an action

2018-02-13T00:02:19+00:00

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