| /openbmc/docs/ |
| H A D | features.md | 5 - [BMCWeb][] HTTP/Web server
6 - [WebUI Vue][] web application
7 - REST Management: [BMCWeb Redfish][], [Phosphor REST APIs][] includes [Host
9 - [D-Bus interfaces][] describes internal interfaces
10 - [D-Bus Object Mapper][]
11 - [Remote KVM][]
12 - [IPMI in band][] and [IPMI out of band][]
13 - Full IPMI 2.0 Compliance with DCMI
14 - SSH based SOL: [How to use][sol how to use]
15 - Power and Cooling Management: [Phosphor Fan Control][]
[all …]
|
| /openbmc/docs/designs/ |
| H A D | certificate-revocation-list.md | 9 This design is to add management interfaces for certificate revocation list in
24 1. [phosphor-certificate-manager](https://github.com/openbmc/phosphor-certificate-manager)
25 owns certificate objects and implements management interfaces; currently
29 2. [BMCWeb](https://github.com/openbmc/bmcweb): the Redfish front-end which
34 [this discussion](https://redfishforum.com/thread/618/resource-certificate-revocation-list?page=1&s…
35 Google doesn't plan on using Redfish interfaces to manage certificates and CRLs.
37 daemon interacts with the OpenBMC certificate management architecture via DBus
44 1. clients shall be able to install/delete/replace CRLs via DBus APIs
53 ### phosphor-dbus-interfaces subsection
56 [Certs](https://github.com/openbmc/phosphor-dbus-interfaces/tree/master/yaml/xyz/openbmc_project/Ce…
[all …]
|
| H A D | physical-topology.md | 27 Changes to phosphor-dbus-interfaces documenting new Associations have been
28 [proposed](https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/46806)
37 - Must represent one-to-many relationships from chassis inventory objects which:
38 - Connect to cables
39 - Contain other chassis and/or are contained by a chassis
40 - Contain storage drives
41 - Are cooled by fans
42 - Are powered by power supplies
43 - Contain processors such as CPUs
44 - Contain memory such as DIMMs
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | README.md | 3 - Provides a mechanism for logging events and errors to the journal.
4 - Creates error entry D-Bus objects when an error is reported/committed.
5 - Persists error entries across power off.
11 - Generic errors used by applications are defined at
12 [phosphor-dbus-interfaces][phosphor-dbus-interfaces].
13 - Generic errors can be used by all the applications by including the generated
14 elog-errors.hpp header file.
16 [phosphor-dbus-interfaces]: https://github.com/openbmc/phosphor-dbus-interfaces
20 - There are errors that are not generic and are very specific to the
22 - Refer to [openpower-debug-collector][openpower-debug-collector].
[all …]
|
| /openbmc/dbus-sensors/ |
| H A D | README.md | 1 # dbus-sensors
3 dbus-sensors is a collection of sensor applications that provide the
4 xyz.openbmc_project.Sensor collection of interfaces. They read sensor values
5 from hwmon, d-bus, or direct driver access to provide readings. Some advance
6 non-sensor features such as fan presence, pwm control, and automatic cpu
11 - runtime re-configurable from d-bus (entity-manager or the like)
13 - isolated: each sensor type is isolated into its own daemon, so a bug in one
17 - async single-threaded: uses sdbusplus/asio bindings
19 - multiple data inputs: hwmon, d-bus, direct driver access
21 ## dbus interfaces
[all …]
|
| /openbmc/phosphor-bmc-code-mgmt/common/include/ |
| H A D | software_manager.hpp | 7 #include <phosphor-logging/lg2.hpp>
15 using namespace phosphor::software::config;
16 using namespace phosphor::software::device;
18 namespace phosphor::software::manager namespace
29 // Fetches initial configuration from dbus and initializes devices.
31 // @param configurationInterfaces the dbus interfaces from which to fetch
40 // This function receives a dbus name and object path for a single device,
44 // @param service The dbus name where our configuration is
67 std::vector<std::string> interfaces);
69 std::vector<std::string> interfaces);
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/dbus/ |
| H A D | phosphor-dbus-interfaces_git.bb | 1 SUMMARY = "Phosphor DBus Interfaces"
2 DESCRIPTION = "Generated bindings, using sdbus++, for the phosphor YAML"
3 LICENSE = "Apache-2.0"
6 ${PYTHON_PN}-sdbus++-native \
14 SRC_URI = "git://github.com/openbmc/phosphor-dbus-interfaces;branch=master;protocol=https"
19 inherit obmc-phosphor-utils
20 inherit phosphor-dbus-yaml
23 # Markdown files are installed into /usr/share/phosphor-dbus-interfaces so
25 FILES:${PN}-doc += "${datadir}/${BPN}"
28 PACKAGES:append = " ${PN}-redfish-registry"
[all …]
|
| /openbmc/docs/designs/inventory/ |
| H A D | gpio-based-hardware-inventory.md | 11 …om/openbmc/docs/blob/46902afd6ebd20d1148379df99fe2c0c591f56ba/designs/gpio-based-cable-presence.md)
26 and focuses on IPMI use-case.
28 …om/openbmc/docs/blob/879601d92becfa1dbc082f487abfb5e0151a5091/designs/gpio-based-cable-presence.md)
31 phosphor-multi-gpio-presence and phosphor-inventory-manager.
34 by phosphor-inventory-manager.
36 The presence daemon then toggles the 'Present' property on dbus interface
39 Additional item-specific properties are statically declared in the
40 phosphor-inventory-manager configuration.
44 …277cdb37e8062ae298402e9685882acb/meta-ibm/meta-sbp1/recipes-phosphor/gpio/phosphor-gpio-monitor/ph…
46 …phosphor-inventory-manager config](https://github.com/openbmc/openbmc/blob/1d438f68277cdb37e8062ae…
[all …]
|
| /openbmc/phosphor-led-sysfs/ |
| H A D | meson.build | 2 'phosphor-ledcontroller',
15 phosphor_dbus_interfaces_dep = dependency('phosphor-dbus-interfaces')
16 phosphor_logging_dep = dependency('phosphor-logging')
34 ['udev' / 'rules.d' / '70-leds.rules'],
40 ['systemd' / 'system' / 'phosphor-ledcontroller.service'],
44 ['systemd' / 'system' / 'sysfs-led@.service'],
48 dbus = dependency('dbus-1') variable
51 'dbus-1' / 'system-services' / 'xyz.openbmc_project.LED.Controller.service',
53 install_dir: dbus.get_variable(pkgconfig: 'system_bus_services_dir'),
57 'interfaces/internal_interface.cpp',
[all …]
|
| /openbmc/docs/architecture/ |
| H A D | sensor-architecture.md | 1 # Sensor Support for OpenBMC using phosphor-hwmon
3 This document describes sensors provided by [phosphor-hwmon][15]. An alternate
4 method is to use the suite of applications provided by [dbus-sensors][16]. While
5 the configuration details between the two methods differ, the D-Bus
10 map sensors to [D-Bus][1] objects. The D-Bus object will broadcast the
15 ## D-Bus
18 Service xyz.openbmc_project.Hwmon-<hash>.Hwmon1
20 Interfaces xyz.openbmc_project.Sensor.[*], others (see below)
27 - **<type\>** : The [HWMon class][2] name in lower case.
28 - Examples include `temperature, fan_tach, voltage`.
[all …]
|
| /openbmc/phosphor-time-manager/ |
| H A D | utils.hpp | 5 #include <phosphor-logging/lg2.hpp>
11 namespace phosphor namespace
21 using Interfaces = std::vector<Interface>; typedef
23 std::vector<std::pair<Path, std::vector<std::pair<Service, Interfaces>>>>;
27 /** @brief The template function to get property from the requested dbus path
29 * @param[in] bus - The Dbus bus object
30 * @param[in] service - The Dbus service name
31 * @param[in] path - The Dbus object path
32 * @param[in] interface - The Dbus interface
33 * @param[in] propertyName - The property name to get
[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
29 repository which is responsible for emitting the dbus signals for every new POST
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…
[all …]
|
| /openbmc/google-misc/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/phosphor-host-postd/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/phosphor-state-manager/ |
| H A D | README.md | 1 # Phosphor State Manager Documentation
6 phosphor-state-manager (PSM) software is its support for requests to power on
15 basic command line support to query and control phosphor-state-manager
17 OpenBMC system and utilizes D-Bus APIs. These D-Bus APIs are used for
20 As with all OpenBMC applications, interfaces and properties within
21 phosphor-state-manager are D-Bus interfaces. These interfaces are then used by
27 phosphor-state-manager makes extensive use of systemd. There is a [writeup][1]
30 phosphor-state-manager monitors for systemd targets to complete as a trigger to
31 updating the its corresponding D-Bus property. When using PSM, a user must
35 phosphor-state-manager follows some basics design guidelines in its
[all …]
|
| /openbmc/service-config-manager/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/phosphor-inventory-manager/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/phosphor-time-manager/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/phosphor-user-manager/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/openpower-occ-control/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/openpower-proc-control/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/phosphor-led-manager/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/phosphor-led-sysfs/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/phosphor-post-code-manager/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|
| /openbmc/phosphor-buttons/subprojects/ |
| H A D | phosphor-dbus-interfaces.wrap | 1 [wrap-git]
2 url = https://github.com/openbmc/phosphor-dbus-interfaces.git
6 phosphor-dbus-interfaces = phosphor_dbus_interfaces_dep
|