#
c4b85b77 |
| 08-Dec-2022 |
Patrick Williams <patrick@stwcx.xyz> |
markdownlint: fix all warnings
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I59c8a25e738da834488e356f15678258636fdd47
|
#
abbcd4a5 |
| 08-Dec-2022 |
Patrick Williams <patrick@stwcx.xyz> |
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: I3608bb85305658ae95c705238800fb20d8841774 Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
show more ...
|
#
809545a6 |
| 21-Dec-2021 |
Andrei Kartashev <a.kartashev@yadro.com> |
Update README file
Remove outdated information about passthrough: x86-power-control do nothing with this and works fine without any passthrough-related patches. Update compile options. Cleanup docum
Update README file
Remove outdated information about passthrough: x86-power-control do nothing with this and works fine without any passthrough-related patches. Update compile options. Cleanup document formatting.
Signed-off-by: Andrei Kartashev <a.kartashev@yadro.com> Change-Id: I370ce124770719365b14146aeb3bfcf998a8ec3a
show more ...
|
#
7012051a |
| 16-Sep-2020 |
Priyatharshan P <priyatharshanp@hcl.com> |
Dbus Based Gpio Event monitoring This change provide the implementation for D-bus based Gpio Event monitoring. For the platform not having direct GPIO access can use dbus based event
Dbus Based Gpio Event monitoring This change provide the implementation for D-bus based Gpio Event monitoring. For the platform not having direct GPIO access can use dbus based event monitor by configuring dbus names in Json file. x86-power-control will monitor the property change from the given DbusName and take appropriate action Updated parsing logic of reading config values from json. TESTED:Tested and verified in Tiogapass and YosemteV2. The existing functionality is not broken after adding the JSON parser implementation in Tiogapass. Signed-off-by: Priyatharshan P <priyatharshanp@hcl.com> Change-Id: I480c62eccebf6d0a3c4609afaf24d55265d99602
show more ...
|
#
fb957331 |
| 28-Jan-2021 |
Jason M. Bills <jason.m.bills@linux.intel.com> |
Add option to use PLT_RST for warm reset detection To support platforms that provide a PLT_RST eSPI signal, this change adds an option to detect warm resets from the eSPI PLT_RST sig
Add option to use PLT_RST for warm reset detection To support platforms that provide a PLT_RST eSPI signal, this change adds an option to detect warm resets from the eSPI PLT_RST signal instead of POST Complete. The eSPI PLT_RST signal is provided by the xyz.openbmc_project.Host.Misc.Manager service. Tested: Confirmed that warm reset can be detected based on PLT_RST changes. Change-Id: I8ac2c260280cf4edec8800e8e2ee12159748f24e Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
show more ...
|
#
f61ca6fd |
| 15-Aug-2019 |
Ed Tanous <ed.tanous@intel.com> |
Reinvent x86 power control application The previous application that was posted here had a TON of timing issues that made it basically unworkable, and was missing several features (l
Reinvent x86 power control application The previous application that was posted here had a TON of timing issues that made it basically unworkable, and was missing several features (like power button override, VR timers, ect) that weren't really possible in the old scheme. This commit shows a reimagining of power control on the AST2500, and seems to work much more reliably in testing across several platforms. The key differentiators here are: 1. It gets rid of the target files. Despite _many_ attempts to make the target file approach reliable across 1000/10000 reboot cycle testings, it was clear that the timing differences in the activation times caused too many hard to fix race conditions. To this end, the power state machine has been moved into c++, where we can be very explicit about our IO, and event timings. 2. It implements several features that were not present in the old implementation, like soft power cycle. These were required to implement the full Redfish ComputerSystem schema properly. 3. It implements proper handling when collisions occur. For example when two power off requests come in at the same time. Because of #1 we can now service both of these requests "correctly" and remove the possibility of desyncronizing the state machine from the host state. A majority of this work was accomplished by Jason Bills. The history is available here, which can be pushed if needed, but I don't beleive it's wanted. https://github.com/Intel-BMC/intel-chassis-control/commits/master Signed-off-by: Ed Tanous <ed.tanous@intel.com> Change-Id: I2eb7fb1dbcab3d374df9d2e8c62407f0277e2583
show more ...
|
#
f9f50395 |
| 02-Aug-2018 |
Brad Bishop <radsquirrel@gmail.com> |
Initial commit
|