#
44872b07 |
| 19-Sep-2022 |
Chau Ly <chaul@amperecomputing.com> |
control: Support target_path option in configuration file
The target path containing the interface xyz.openbmc_project.control.FanPwm or xyz.openbmc_project.control.FanSpeed can be different between
control: Support target_path option in configuration file
The target path containing the interface xyz.openbmc_project.control.FanPwm or xyz.openbmc_project.control.FanSpeed can be different between phosphor-hwmon and dbus-sensor.
In phosphor-hwmon, it is "/xyz/openbmc_project/sensors/fan_tach/". In dbus-sensor, it is "/xyz/openbmc_project/control/fanpwm/"
This commit supports making this path configurable via "target_path". By default, it is "/xyz/openbmc_project/sensors/fan_tach/".
Signed-off-by: Chau Ly <chaul@amperecomputing.com> Change-Id: Id799986ff69455b7c7054070ed2ab3b2e2500a6c
show more ...
|
#
cb356d48 |
| 22-Jul-2022 |
Patrick Williams <patrick@stwcx.xyz> |
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: I9029cc722e7712633c15436bd3868d8c3209f567
show more ...
|
#
3ea9ec2b |
| 19-Nov-2021 |
Patrick Williams <patrick@stwcx.xyz> |
sdbusplus: remove usage of deprecated alias
The alias `server::match` has been deprecated since 2016. Use the new alias under bus.
Change-Id: I21baf6b70401d996519b5940d0cd685535475a2f Signed-off-b
sdbusplus: remove usage of deprecated alias
The alias `server::match` has been deprecated since 2016. Use the new alias under bus.
Change-Id: I21baf6b70401d996519b5940d0cd685535475a2f Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
show more ...
|
#
3e1bb274 |
| 26-May-2020 |
Matthew Barth <msbarth@us.ibm.com> |
control: Clang format updates
Used `format-code.sh` build script to make changes to conform to clang format.
Tested: Compiled
Change-Id: Ic9d621d7c5647bde0a92c5f17938c99deeca0512 Signed-off-by: Ma
control: Clang format updates
Used `format-code.sh` build script to make changes to conform to clang format.
Tested: Compiled
Change-Id: Ic9d621d7c5647bde0a92c5f17938c99deeca0512 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
c21d0b36 |
| 13-May-2020 |
Patrick Williams <patrick@stwcx.xyz> |
sdbusplus: replace message::variant with std::variant
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I7b2bc0a8b34e4d276c0e8ea2243459aab4e1c177
|
#
7f4c548d |
| 07-Feb-2020 |
Matthew Barth <msbarth@us.ibm.com> |
Support sensor value property to type double
Constructed an intermediate function that is used to apply a visitor against the `xyz.openbmc_project.Sensor.Value` interface's `Value` property. This fu
Support sensor value property to type double
Constructed an intermediate function that is used to apply a visitor against the `xyz.openbmc_project.Sensor.Value` interface's `Value` property. This function is called to apply the visitor at each point the internally cached sensor value is updated and stores it as the data type that is given for this property within the configured yaml.
The visitor provides storing the sensor value directly where the data type configured matches the data type of the `Value` property on dbus. However, in the case where the configured data type is the original int64 and the data type on dbus is double, the visitor will scale the value from dbus to millidegree C(as it was when stored as an int64 on dbus) and cast it to the configured int64 data type. This resulting cast value is stored within the internal cache now as an int64 until the machine configuration yaml file is updated to reflect the change in the sensor's value data type to be a double.
Tested: No change with use of sensor value as int64 and configured as int64 No change with use of sensor value as double and configured as int64 Witherspoon fan control functions correctly with use of sensor value as double and configuration updated to utilize as a double
Change-Id: Ieb0a646ea37bf7991b9b1f94a85977d9e8984e60 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
a422bbe4 |
| 18-Sep-2019 |
Matthew Barth <msbarth@us.ibm.com> |
Support int32 property variant type
Change-Id: I19d426e00b4ce1cb31d4dbc428caa5749e012322 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
#
75d97350 |
| 01-Nov-2018 |
Matthew Barth <msbarth@us.ibm.com> |
Create empty action groups
This introduces the framework for set speed events to have the groups within an event assign directly on the event action. When a group is defined directly to an action, i
Create empty action groups
This introduces the framework for set speed events to have the groups within an event assign directly on the event action. When a group is defined directly to an action, it will be used in place of the group(s) on the event. This allows a single event, driven by trigger(s), to call multiple actions on different groups with differing parameters to those actions.
Change-Id: I5c648d912641b3006a77eab27457e3ddb220c2ad Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
2885ba90 |
| 14-Nov-2018 |
Matthew Barth <msbarth@us.ibm.com> |
Provide event name to triggers
Change-Id: Iec063b39a3e3e6a63038a2013f42e8a69ad9fadf Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
#
621a5778 |
| 14-Nov-2018 |
Matthew Barth <msbarth@us.ibm.com> |
Add event name to SetSpeedEvent data
Change-Id: Ida95790d78d016952da7d2a2afa0940edbe0aa7b Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
|
#
926df663 |
| 09-Oct-2018 |
Matthew Barth <msbarth@us.ibm.com> |
Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the associated event trigger is chosen, what's generated to retrieve the dbus data i
Separate handlers for signals and method calls
Signals and method calls have different parameter structures. When the associated event trigger is chosen, what's generated to retrieve the dbus data is specific to that trigger event. For signals, the data is read from the given signal message. A method call is method specific and is called to be done against all of the members within the event group.
Change-Id: I92cbdbf05852fbaa7f1b56ed518e30278cdf840b Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
146b7390 |
| 08-Mar-2018 |
Matthew Barth <msbarth@us.ibm.com> |
Convert event group to a vector of tuples
In preparation for storing each event group member's property state used within the event's actions, the group type should be converted to a vector of tuple
Convert event group to a vector of tuples
In preparation for storing each event group member's property state used within the event's actions, the group type should be converted to a vector of tuples. This vector will allow, if user defines, easier use of different interfaces and properties on the same path to be used within the same event group.
Tested: Generated code for groups reflects vector instead of map Actions against groups remain unchanged
Change-Id: I9f4bb609de424d9004d43524fd04737a50fb2c6f Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
016bd24c |
| 07-Mar-2018 |
Matthew Barth <msbarth@us.ibm.com> |
Move signals to event triggers
Move the generation and initialization of signals to be included in the available event triggers. The signal trigger consists of subscribing to a given signal match wh
Move signals to event triggers
Move the generation and initialization of signals to be included in the available event triggers. The signal trigger consists of subscribing to a given signal match where when the signal is received and handled, it causes the event actions to be called.
Tested: All current event signals are still registered and received Speed changes occur based on temperature sensor change signals
Change-Id: Iab4ccabb50ad910d5d566bd8c1922109638bd760 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
1b4de26a |
| 06-Mar-2018 |
Matthew Barth <msbarth@us.ibm.com> |
Call event triggers on initialization
Move timers to be an event trigger function that is called upon event initialization. Previously, event timers were created and started directly within the init
Call event triggers on initialization
Move timers to be an event trigger function that is called upon event initialization. Previously, event timers were created and started directly within the initialization of the event, this moves the creation and starting of a defined event timer to within a selectable event trigger function.
With the creation of event triggers, an event can be defined with a list of supported triggers used to execute the actions, if defined, of the event. In the case no actions are given, the trigger is still used.
Tested: Timer triggers are created/started correctly for an event Events with no actions have timers created/started as defined
Change-Id: I9ab13a4269b2035095cadbbe2c613a16df469589 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
d0b90fc6 |
| 05-Mar-2018 |
Matthew Barth <msbarth@us.ibm.com> |
Have timers be a trigger type in microseconds
Extract and generate timers in microseconds for all event triggers and actions that take a timer as a parameter.
Tested: Timers are created on even
Have timers be a trigger type in microseconds
Extract and generate timers in microseconds for all event triggers and actions that take a timer as a parameter.
Tested: Timers are created on events with timer triggers defined Inspect that generated timers are created in microseconds No timer is created for events without a timer trigger
Change-Id: I345f247782779ef142fe0d569632be2b6c11f0c3 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
1b3e9602 |
| 13-Feb-2019 |
Matthew Barth <msbarth@us.ibm.com> |
Add framework to set properties on a zone
Properties hosted by a zone object need the ability to be set upon zone initialization. This adds support to allow the zone configuration yaml to contain wh
Add framework to set properties on a zone
Properties hosted by a zone object need the ability to be set upon zone initialization. This adds support to allow the zone configuration yaml to contain what properties to set and with what values on a zone. The parser updates to generate what uses this framework is in a followup commit.
Change-Id: I9fd93746cc097f05869400451daff03cf3ef89b7 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
8fd879fb |
| 30-Oct-2018 |
William A. Kennington III <wak@google.com> |
Remove timer in favor of sdeventplus/utility/timer
This removes the custom timer implementation and moves to the sdeventplus utility. Functionally this should make no change
Tested: Built and r
Remove timer in favor of sdeventplus/utility/timer
This removes the custom timer implementation and moves to the sdeventplus utility. Functionally this should make no change
Tested: Built and run through the unit test suite.
Change-Id: Ib7ee90d489d5db72496aaaca91c3cf5490ad47d6 Signed-off-by: William A. Kennington III <wak@google.com>
show more ...
|
#
122b843f |
| 30-Oct-2018 |
William A. Kennington III <wak@google.com> |
control: Rename Timer -> TimerConf
It is confusing to read some of the type definitions that deal with timers when Timer could mean a timer instantiation or a set of timer configuration parameters.
control: Rename Timer -> TimerConf
It is confusing to read some of the type definitions that deal with timers when Timer could mean a timer instantiation or a set of timer configuration parameters. This change disambiguates the two types.
Tested: Built and run through unit tests.
Change-Id: I9dd6b47886747d56a86b6a50eb9a74a331d0a1fe Signed-off-by: William A. Kennington III <wak@google.com>
show more ...
|
#
0ce353ec |
| 30-Oct-2018 |
William A. Kennington III <wak@google.com> |
control: Alias TimerType locally
This is needed for a future commit that removes the local phosphor::util::Timer implementation.
Tested: Built and run through unit tests.
Change-Id: I8ea3399fe
control: Alias TimerType locally
This is needed for a future commit that removes the local phosphor::util::Timer implementation.
Tested: Built and run through unit tests.
Change-Id: I8ea3399fec8761055d4a0d94fb9ea91fd34040ea Signed-off-by: William A. Kennington III <wak@google.com>
show more ...
|
#
069e4405 |
| 31-Jan-2018 |
Lei YU <mine260309@gmail.com> |
Add target interface for fan control
Current fan control assumes the use of the FanSpeed interface for fan targets. For fans controlled by pwm, FanPwm interface is added.
This commit adds "target_i
Add target interface for fan control
Current fan control assumes the use of the FanSpeed interface for fan targets. For fans controlled by pwm, FanPwm interface is added.
This commit adds "target_interface" config parameter, so that user can specify the interface for the fan targets.
E.g.
- inventory: /system/chassis/motherboard/fan0 cooling_zone: 0 cooling_profile: air sensors: - fan0 target_interface: xyz.openbmc_project.Control.FanPwm
The config is optional and defaults to FanSpeed, so the current code will not be affected.
Tested: Use this config on Romulus, ensures the fan control sets target on FanPwm interface and works fine.
Change-Id: I73adccaa770d657b5d7aaeb307917f89588524de Signed-off-by: Lei YU <mine260309@gmail.com>
show more ...
|
#
9a5b6994 |
| 23-Jan-2018 |
Matthew Barth <msbarth@us.ibm.com> |
Support properties of type string
Properties used within set speed events may be of type string to trigger an action. These should be handled where the defined type attribute is given as 'std::strin
Support properties of type string
Properties used within set speed events may be of type string to trigger an action. These should be handled where the defined type attribute is given as 'std::string' and a parsed value is an instance of python str type.
Resolves openbmc/openbmc#292
Change-Id: Ib188e7abc212062a1c61950abaa28434a4726521 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
bfb1a566 |
| 05-Oct-2017 |
Matthew Barth <msbarth@us.ibm.com> |
Add timer event management
Events defined to have timers require the ability to find a timer, add a timer to the event, and removing a timer event entirely. These event timers are intended to allow
Add timer event management
Events defined to have timers require the ability to find a timer, add a timer to the event, and removing a timer event entirely. These event timers are intended to allow actions based on the event to be delayed or recurring based on the timer defined.
Change-Id: Ieaf26f031c5e5aac9472e92354bfb76392642cb4 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
7b7ceb8d |
| 04-Oct-2017 |
Matthew Barth <msbarth@us.ibm.com> |
Add timer type for set speed event timers
This is the first step towards allowing timer driven and/or wrapped actions where the timer interval and type will be defined by the user.
Change-Id: If008
Add timer type for set speed event timers
This is the first step towards allowing timer driven and/or wrapped actions where the timer interval and type will be defined by the user.
Change-Id: If008fda5a2b73117e869f93223e0bfe61290f858 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
e59fdf70 |
| 27-Sep-2017 |
Matthew Barth <msbarth@us.ibm.com> |
Set/update a service name owner for a group
Adds a service name associated with a group when the group or given service name is not found within the map of services otherwise updates the service nam
Set/update a service name owner for a group
Adds a service name associated with a group when the group or given service name is not found within the map of services otherwise updates the service name owner associated with the group.
Change-Id: I602ddaa7e06e354e01ea70d6c5c0a45e74a14e99 Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|
#
336f18a5 |
| 26-Sep-2017 |
Matthew Barth <msbarth@us.ibm.com> |
Update event initialization
Using a null dbus message to the event signal will perform the necessary steps to initialize the event parameters using the given signal handler's function directly.
i.e
Update event initialization
Using a null dbus message to the event signal will perform the necessary steps to initialize the event parameters using the given signal handler's function directly.
i.e.) In the case for subscribing to PropertiesChanged signals, initially the given property must be read. When the PropertiesChanged signal struct is given a null message, it finds the property, reads the value, and then can perform the given signal handler function directly. This produces the same functional path as receiving a PropertiesChanged signal containing the property value within the message.
Change-Id: I35575cfff66eb0305156be786cb1f5536d42bb1c Signed-off-by: Matthew Barth <msbarth@us.ibm.com>
show more ...
|