#
f5402197 |
| 16-Aug-2024 |
Patrick Williams <patrick@stwcx.xyz> |
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: I7b90380845efee6bf6a1fe342a793d71aa9ff181 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
show more ...
|
#
48781aef |
| 10-May-2023 |
Patrick Williams <patrick@stwcx.xyz> |
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: If66f68c96df4baf8dc07abf8729a3cb7657e932d Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
show more ...
|
#
8acaf547 |
| 30-Mar-2021 |
Shawn McCarney <shawnmm@us.ibm.com> |
regulators: Wait for compatible system types There are two options for naming the JSON configuration file: 1. Default name 2. Name based on compatible system types provided by Entity
regulators: Wait for compatible system types There are two options for naming the JSON configuration file: 1. Default name 2. Name based on compatible system types provided by EntityManager If option #2 is used, there is no guarantee that EntityManager will have published the compatible systems types on D-Bus before a boot is attempted. This is not common, but the problem has occurred. When the boot begins, the regulators application configures the voltage regulators. If the config file has not been found and loaded, this configuration cannot occur. This commit enhances the regulators application to wait for EntityManager to publish the compatible systems information during the boot so that the regulators can be configured. A maximum wait time is enforced to prevent the boot from being blocked indefinitely. If this maximum wait time is reached, a critical error is logged indicating that the voltage regulators could not be configured. Tested: * System types available before boot * Have to wait for system types during boot * System types found within 5 minutes * System types not found within 5 minutes * For complete test plan details, see https://gist.github.com/smccarney/b059a5f4da1a9138af770217cbafaea3 Signed-off-by: Shawn McCarney <shawnmm@us.ibm.com> Change-Id: I700a376b94603f36defd1fe266c0a2d7e2a9d30b
show more ...
|
#
cd9ab087 |
| 13-Apr-2020 |
Matthew Barth <msbarth@us.ibm.com> |
regs: Create regulator control utility function The regulator control program will call methods on the phosphor-regulators service to control the mode in which the phosphor-regulator
regs: Create regulator control utility function The regulator control program will call methods on the phosphor-regulators service to control the mode in which the phosphor-regulators application should run in. Tested: Dbus method call occurs against the phosphor-regulators service Signed-off-by: Matthew Barth <msbarth@us.ibm.com> Change-Id: Ib5829f271883bee2ebd52d33cb75da603752e0ae
show more ...
|