| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | IPMI.interface.yaml | 2 Implement to provide an IPMI System Event Log (SEL) logging interface under
5 SEL records store system event information and will contain a record ID and
6 type followed by type-specific information. The type-specific information
8 adding the SEL record), sensor number, event direction and event-specific
12 events it requires a generator ID (0x20 for BMC), sensor D-Bus path, event
13 direction (assertion or de-assertion), and event specific data. For OEM type
19 - name: IpmiSelAdd
21 Log a system event record type SEL entry.
23 - name: Message
26 The text to log for the event.
[all …]
|
| /openbmc/phosphor-buttons/inc/ |
| H A D | button_interface.hpp | 7 #include <phosphor-logging/elog-errors.hpp>
13 ButtonIface(sdbusplus::bus_t& bus, EventPtr& event, ButtonConfig& buttonCfg, in ButtonIface() argument
15 bus(bus), event(event), config(buttonCfg), callbackHandler(handler) in ButtonIface()
17 int ret = -1; in ButtonIface()
44 * @brief This method is called from sd-event provided callback function
45 * callbackHandler if platform specific event handling is needed then a
46 * derived class instance with its specific evend handling logic along with
47 * init() function can be created to override the default event handling.
57 buttonIface->handleEvent(es, fd, revents); in EventHandler()
70 * @brief oem specific initialization can be done under init function.
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Event.v1_11_1.json | 2 "$id": "http://redfish.dmtf.org/schemas/v1/Event.v1_11_1.json",
3 "$ref": "#/definitions/Event",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 "description": "Details for a CPER section or record associated with an event.",
38 …his object shall contain the details for a CPER section or record that is the source of an event.",
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| H A D | LogEntry.v1_19_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
68 …operties contained in this object shall conform to the Redfish Specification-described requirement…
74 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
118 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | Event.v1_11_1.json | 2 "$id": "http://redfish.dmtf.org/schemas/v1/Event.v1_11_1.json",
3 "$ref": "#/definitions/Event",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 "description": "Details for a CPER section or record associated with an event.",
38 …his object shall contain the details for a CPER section or record that is the source of an event.",
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
[all …]
|
| H A D | LogEntry.v1_19_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
68 …operties contained in this object shall conform to the Redfish Specification-described requirement…
74 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
118 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
[all …]
|
| /openbmc/phosphor-debug-collector/ |
| H A D | watch.hpp | 6 #include <systemd/sd-event.h>
19 // User specific call back function input map(path:event) type.
22 // User specific callback function wrapper type.
29 * The inotify watch is hooked up with sd-event, so that on call back,
36 /** @brief ctor - hook inotify watch with sd-event
38 * @param[in] eventObj - Event loop object
39 * @param[in] flags - inotify flags
40 * @param[in] mask - Mask of events
41 * @param[in] events - Events to be watched
42 * @param[in] path - File path to be watched
[all …]
|
| /openbmc/openpower-proc-control/extensions/phal/ |
| H A D | clock_logger.hpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
13 * See the License for the specific language governing permissions and
27 /* Dbus event timer */
31 * @class Manager - Represents the clock daily management functions
48 * @param[in] event - sdeventplus event loop
50 Manager(const sdeventplus::Event& event);
68 * @brief Add processor specific CFAM data to daily logger.
70 * @param[in] proc - pdbg processor target
71 * @param[out] ffdcData - reference to clock data log
77 * @brief Add clock specific register data to daily logger.
[all …]
|
| /openbmc/intel-ipmi-oem/docs/ |
| H A D | Intel_IPMI_Platform_Events.md | 3 In many cases Manufacturers-specific IPMI Platfrom Events are stored in binary
4 form in System Event Log making it very difficult to easily understand platfrom
8 events originating from Intel Management Engine (ME) is used as a case-study.
9 General design of the solution is followed by tailored-down implementation for
14 - **IPMI** - Intelligent Platform Management Interface; standarized binary
16 - **Platform Event** - specific type of IPMI binary payload, used for encoding
17 and sending asynchronous one-way messages to recipient `[1]-29.3`
18 - **ME** - Intel Management Engine, autonomous subsystem used for remote
20 - **Redfish** - modern datacenter management protocol, built around REST
22 - **OpenBMC** - open-source BMC implementation with Redfish-oriented interface
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/ |
| H A D | Create.interface.yaml | 7 /xyz/openbmc_project/dump/<dump type>. On multi-host or on multi-BMC systems
9 /xyz/openbmc_project/dump/<dump type><instance-id>.
12 - name: CreateDump
16 - name: AdditionalData
20 this case should be an implementation specific enum defined for
21 the specific type of dump either in xyz or in a domain. The
23 enum-format string is required to come from a parallel class
24 with this specific Enum name. All of the Enum strings should be
34 - name: Path
41 - xyz.openbmc_project.Common.File.Error.Open
[all …]
|
| /openbmc/phosphor-gpio-monitor/ |
| H A D | README.md | 5 ### `phosphor-gpio-monitor`
12 ### `phosphor-multi-gpio-monitor`
14 This daemon accepts command line parameter as a well-defined GPIO configuration
20 New implementation (phosphor-multi-gpio-monitor) provides multiple gpio line
21 monitoring in single instance of phosphor-multi-gpio-monitor running. It is very
27 There is a phosphor-multi-gpio-monitor.json file that defines details of GPIOs
29 specific configuration file via bbappend.
34 2. LineName: this is the line name defined in device tree for specific gpio
38 5. EventMon: Event of gpio to be monitored. This can be "FALLING", "RISING" OR
41 triggering event. A journal entry will be added for every event occurs
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/.github/workflows/ |
| H A D | yocto-layer.yml | 1 # SPDX-FileCopyrightText: Andrei Gherzan <andrei.gherzan@huawei.com>
3 # SPDX-License-Identifier: MIT
5 ---
13 yocto-check-layer:
14 name: Validate with yocto-check-layer
15 runs-on: [self-hosted, Linux]
17 - name: Checkout the code
20 fetch-depth: 0
21 - name: Define Yocto build files
22 id: changed-files-specific
[all …]
|
| H A D | yocto-builds.yml | 1 # SPDX-FileCopyrightText: Andrei Gherzan <andrei.gherzan@huawei.com>
3 # SPDX-License-Identifier: MIT
5 ---
15 fail-fast: true
18 - raspberrypi
19 - raspberrypi0-2w-64
20 - raspberrypi0-2w
21 - raspberrypi0
22 - raspberrypi0-wifi
23 - raspberrypi2
[all …]
|
| /openbmc/phosphor-buttons/src/ |
| H A D | debugHostSelector_button.cpp | 22 * @brief This method is called from sd-event provided callback function
23 * callbackHandler if platform specific event handling is needed then a
24 * derived class instance with its specific event handling logic along with
25 * init() function can be created to override the default event handling
31 int n = -1; in handleEvent()
|
| /openbmc/qemu/qapi/ |
| H A D | run-state.json | 1 # -*- Mode: Python -*-
18 # @finish-migrate: guest is paused to finish the migration process
22 # the end of the migration. This depends on the command-line -S
26 # @internal-error: An internal error that prevents further guest
29 # @io-error: the last IOP has failed and the device is configured to
36 # @prelaunch: QEMU was started with -S and guest has not started
38 # @restore-vm: guest is paused to restore VM state
42 # @save-vm: guest is paused to save the VM state
44 # @shutdown: guest is shut down (and -no-shutdown is in use)
51 # @guest-panicked: guest has been panicked as a result of guest OS
[all …]
|
| /openbmc/phosphor-post-code-manager/ |
| H A D | README.md | 1 # phosphor-post-code-manager
3 This phosphor-post-code-manager repository provides an infrastructure to persist
9 To build phosphor-post-code-manager package , do the following steps:
13 ninja -C <build directory>
20 [template version](https://github.com/openbmc/docs/blob/master/designs/multi-host-postcode.md)
22 [dbus interfaces & methods](https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xy…
28 [phosphor-host-postd](https://github.com/openbmc/phosphor-host-postd) OpenBMC
32 phosphor-post-code-manager is architected to look for the property changed
34 [Value](https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/St…
37 [redfish](https://github.com/openbmc/docs/blob/master/designs/redfish-postcodes.md)
[all …]
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | blkdebug.rst | 5 Copyright (C) 2014-2015 Red Hat Inc
8 the COPYING file in the top-level directory.
10 The ``blkdebug`` block driver is a rule-based error injection engine. It can be
17 ----------
23 Error injection allows test cases to trigger I/O errors at specific points.
27 -----
35 follows the same .ini-like format used by QEMU's ``-readconfig`` option, and
41 [inject-error]
42 event = "read_aio"
47 ``/usr/include/asm-generic/errno-base.h`` for errno values.
[all …]
|
| /openbmc/phosphor-fan-presence/control/json/ |
| H A D | event.hpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
13 * See the License for the specific language governing permissions and
36 * @class Event - Represents a configured fan control event
39 * also optional. An event object can be used to enable a specific change to
49 class Event : public ConfigBase class
55 Event() = delete;
56 Event(const Event&) = delete;
57 Event(Event&&) = delete;
58 Event& operator=(const Event&) = delete;
59 Event& operator=(Event&&) = delete;
[all …]
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | Net-SNMP | 1 ---- Part 1: CMU/UCD copyright notice: (BSD like) -----
5 …Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of Calif…
9 …rtising or publicity pertaining to distribution of the software without specific written permissio…
11 …E, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE R…
13 ---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----
15 Copyright (c) 2001-2003, Networks Associates Technology, Inc All rights reserved. Redistribution an…
19 … used to endorse or promote products derived from this software without specific prior written per…
21 …ERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGH…
23 ---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----
25 Portions of this code are copyright (c) 2001-2003, Cambridge Broadband Ltd. All rights reserved. Re…
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-core/sdbus-c++/sdbus-c++-libsystemd/ |
| H A D | 0020-sd-event-Make-malloc_trim-conditional-on-glibc.patch | 3 Date: Wed, 2 Aug 2023 12:06:27 -0700
4 Subject: [PATCH 20/22] sd-event: Make malloc_trim() conditional on glibc
8 Upstream-Status: Inappropriate [musl-specific]
9 Signed-off-by: Khem Raj <raj.khem@gmail.com>
10 ---
11 src/libsystemd/sd-event/sd-event.c | 4 +++-
12 1 file changed, 3 insertions(+), 1 deletion(-)
14 diff --git a/src/libsystemd/sd-event/sd-event.c b/src/libsystemd/sd-event/sd-event.c
16 --- a/src/libsystemd/sd-event/sd-event.c
17 +++ b/src/libsystemd/sd-event/sd-event.c
[all …]
|
| /openbmc/openbmc/poky/meta/recipes-core/systemd/systemd/ |
| H A D | 0020-sd-event-Make-malloc_trim-conditional-on-glibc.patch | 3 Date: Wed, 2 Aug 2023 12:06:27 -0700
4 Subject: [PATCH 20/26] sd-event: Make malloc_trim() conditional on glibc
8 Upstream-Status: Inappropriate [musl-specific]
9 Signed-off-by: Khem Raj <raj.khem@gmail.com>
10 ---
11 src/libsystemd/sd-event/sd-event.c | 4 +++-
12 1 file changed, 3 insertions(+), 1 deletion(-)
14 diff --git a/src/libsystemd/sd-event/sd-event.c b/src/libsystemd/sd-event/sd-event.c
16 --- a/src/libsystemd/sd-event/sd-event.c
17 +++ b/src/libsystemd/sd-event/sd-event.c
[all …]
|
| /openbmc/qemu/trace/ |
| H A D | event-internal.h | 4 * Copyright (C) 2012-2016 Lluís Vilanova <vilanova@ac.upc.edu>
7 * See the COPYING file in the top-level directory.
15 * that the event is not VCPU specific
17 #define TRACE_VCPU_EVENT_NONE ((uint32_t)-1)
21 * @id: Unique event identifier.
22 * @name: Event name.
26 * Interpretation of @dstate depends on whether the event has the 'vcpu'
28 * - false: Boolean value indicating whether the event is active.
29 * - true : Integral counting the number of vCPUs that have this event enabled.
31 * Opaque generic description of a tracing event.
|
| /openbmc/docs/designs/ |
| H A D | multihost-phosphor-buttons.md | 1 # Multi-host front panel phosphor buttons interface
13 reset buttons and trigger power event handlers.
15 phosphor-buttons currently only support push type buttons.support for different
18 additional input types in phosphor button interfaces and event handling.
28 corresponding to platform specific hardware buttons/MUX/Switches which are
38 +----------------------------------------------+
42 | +--------------+ +--------------+ |
46 | +--------------+ +--------------+ |
51 +----------------------------------------------+
54 platform specific front panel may contain additional hardware buttons or mux
[all …]
|
| /openbmc/qemu/docs/specs/ |
| H A D | acpi_cpu_hotplug.rst | 1 QEMU<->ACPI BIOS CPU hotplug interface
7 ACPI BIOS GPE.2 handler is dedicated for notifying OS about CPU hot-add
8 and hot-remove events.
12 -------------------------------------------
16 - ICH9-LPC (IO port 0x0cd8-0xcf7, 1-byte access)
17 - PIIX-PM (IO port 0xaf00-0xaf1f, 1-byte access)
18 - One bit per CPU. Bit position reflects corresponding CPU APIC ID. Read-only.
19 - The first DWORD in bitmap is used in write mode to switch from legacy
22 QEMU sets corresponding CPU bit on hot-add event and issues SCI
23 with GPE.2 event set. CPU present map is read by ACPI BIOS GPE.2 handler
[all …]
|
| /openbmc/phosphor-fan-presence/ |
| H A D | sdeventplus.hpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
13 * See the License for the specific language governing permissions and
18 #include <sdeventplus/event.hpp>
24 * @brief Event access delegate implementation for sdeventplus.
30 * @brief Get the event instance
34 static auto event = sdeventplus::Event::get_default(); in getEvent() local
35 return event; in getEvent()
|